Binding a CCE Cluster

Before deploying components in a Kubernetes environment, bind only one CCE cluster to the environment so that components can be deployed and run in the Kubernetes environment.

Prerequisites

A CCE cluster to be bound has been created and is in the running state. The cluster must be in the same VPC as the target environment and cannot be managed by other environments. CCE clusters are used to deploy and run components in Kubernetes environments.
- For details about how to create a CCE cluster, see Buying a Cluster. Create a CCE Turbo or CCE Standard cluster based on your service requirements.
  If you create a CCE Turbo cluster, set SNAT rules for the cluster so that the cluster can access the public network through the NAT gateway to pull source code. Otherwise, when the source code is used to deploy a component in container-based deployment or a source code-build task is executed, the source code fails to be obtained because the public network cannot be accessed. As a result, the component deployment or build fails. For details about how to set SNAT rules for the cluster, see Accessing the Internet from a Container.
- For details about how to add a node to the CCE cluster, see Creating a Node.
- ServiceStage supports Elastic Cloud Server (VM) and BMS nodes in CCE clusters.
- For details about the OSs supported by CCE cluster nodes, see Node OS.
- Container engines of CCE cluster nodes support Docker and Containerd. For details about relationship between node OSs and container engines, see Container Engine.
A Kubernetes environment has been created. For details, see Creating an Environment.

Binding a CCE Cluster

Log in to ServiceStage.
On the Environment Management page, click the target environment.
In the Resources area, choose Clusters from Compute.
Click Bind now.
- If the CCE cluster to be bound has been created, select the cluster from the cluster drop-down list and click OK.
- If no CCE cluster is created, go to the CCE console as prompted, create a CCE cluster by referring to Prerequisites, and bind the CCE cluster.
In a Kubernetes environment, if IPv6 is enabled for the selected VPC and CCE clusters are managed, select a CCE cluster with IPv6 enabled. Otherwise, the Java chassis microservice registered on the exclusive microservice engine with security authentication enabled in the VPC fails to register the discovery address using IPv6.

For details, see What Should I Do If the Service Registration Fails After IPv6 Is Enabled for the Exclusive Microservice Engine with Security Authentication Enabled?