Namespace Overview
A namespace is the fundamental unit for resource isolation and network planning in CCI. All pods must run within a designated namespace.
Use Cases
Create separate namespaces by service line (for example, frontend and backend) or environment (for example, development, testing, and production) to enforce logical isolation.
Network Integration
When creating a namespace, you must associate it with a VPC and subnet. Once bound, all containers in the namespace are automatically connected to the VPC network and can communicate with other cloud services over the private network.
Important Notes
After a namespace is created, the associated VPC and subnet cannot be changed. If network planning is incorrect, you must delete the namespace and recreate it.
Billing
Namespaces are free of charge. You are billed only for the container instances (vCPUs and memory) running within them.
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.
For any further questions, feel free to contact us through the chatbot.
Chatbot
