Overview

To make it easier for you to bind an EIP to a pod in CCI, you only need to configure the annotation when creating the pod. The EIP will be automatically bound to the pod.

Constraints

A pod can only have one EIP bound, and an EIP can only be bound to one pod.
You can set annotations when creating a pod. After the pod is created, the annotations related to the EIP cannot be updated.
The EIP allocated during pod creation takes precedence over the EIP created by an EIPPool.
When you create a pod, binding an existing EIP has priority over binding a new EIP.
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.
For an EIP that has been bound to a pod, do not perform operations such as changing the alias, deleting, unbinding, and binding the EIP, and changing the billing mode on the EIP console or through APIs. Otherwise, some resources may not be deleted.
If an existing EIP is to be bound to the pod and the pod is deleted and then rebuilt, the time for the new pod to be ready is prolonged because the EIP needs to be unbound from the old pod.
An existing EIP must be one that is manually allocated. An EIP created using an EIPPool cannot be used, or the EIP status will be abnormal.