Help Center/
Cloud Container Instance (CCI)/
User Guide/
Using CCI Through the Console/
Network Management/
Configuring an EIP for a Pod/
EIP Overview
Updated on 2025-09-26 GMT+08:00
EIP 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.
- When you create a pod, binding an existing EIP has a priority 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, 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.
More Operations
You can perform the following operations on EIPs:
Parent topic: Configuring an EIP for a Pod
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
The system is busy. Please try again later.
For any further questions, feel free to contact us through the chatbot.
Chatbot