Overview

CCI introduces a user-defined resource object named EIPPool to automatically bind EIPs to pods. EIPPools support two EIP resource management modes: dynamic mode (EIP resources are automatically created by CCI) and static mode (EIP resources are created by users in advance).

Constraints

Only one EIP can be bound to a pod.
To enable a pod with an EIP bound to be accessed from the public network, you need to add security group rules to allow access from the public network.
An EIPPool being used by a pod cannot be deleted. You need to delete the associated pod and then delete the EIPPool.
EIPPools are namespace-level resources and cannot be used across namespaces.
In the rolling upgrade of a workload, by default, new pods are created before old pods are deleted (for details, see the upgrade policy). As a result, the upgrade may fail due to insufficient EIPs in the EIPPool. To avoid this, you can set the number of EIPs in the EIPPool to be slightly greater than the total number of Deployment replicas that use the EIPPool, or set maxSurge to 0.