EIP Overview

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

Notes and Constraints

A pod can only have one EIP bound, and an EIP can only be bound to one pod.
You can set the required annotation when creating a pod. After the pod is created, the annotation for binding the EIP cannot be updated.
When you create a pod, the priority of binding an existing EIP to the pod is higher than that of 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, you cannot 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.
An EIP cannot be bound directly to a workload. EIP binding is supported only for single-pod workloads. To expose a multi-pod workload to the public internet, use a LoadBalancer Service or NAT gateway.