Binding a CCE Cluster

After Creating a Kubernetes Environment in Resource Management Mode, you need to bind a CCE cluster to the environment to deploy and run components in the Kubernetes environment.

In an HA environment, bind one CCE cluster to each AZ.
In a non-HA environment, bind one CCE cluster.

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 a Kubernetes Environment in Resource Management Mode.

Binding a CCE Cluster

Log in to ServiceStage.
Choose Environment Management. The Environment Management page is displayed.
Click the target environment. The Overview page is displayed.
Choose Cloud Container Engine from Compute.

Click Bind now.

If a CCE cluster has been created, bind it to the environment by referring to the following table.

HA Environment or Not	How to Bind
Yes	NOTE: In an HA environment, the AZ where the master node of the cluster to be bound is located and the AZ where the nodes running workloads in the cluster are located must be the same as the AZ selected when the cluster is bound. Select an AZ from the AZ drop-down list. Select a CCE cluster that can be bound in the AZ from the Cluster drop-down list. Click OK. Click Add Cluster. Select another AZ from the AZ drop-down list. Select a CCE cluster that can be bound in the AZ from the Cluster drop-down list. Click OK.
No	Select the cluster to be bound from the Cluster drop-down list. Select the namespace to be bound to the CCE cluster from the Namespace drop-down list. When you create and deploy a component in an environment bound with a CCE cluster, the namespace bound to the CCE cluster is specified. During component creation and deployment, if the current environment is used to build component images, this namespace is used to isolate build data by default. It is also used to isolate created component instances by default. After binding a cluster, you can bind a new namespace to the cluster based on service requirements. For details, see Binding a Namespace. Click OK.

HA Environment or Not

How to Bind

Yes

NOTE:

In an HA environment, the AZ where the master node of the cluster to be bound is located and the AZ where the nodes running workloads in the cluster are located must be the same as the AZ selected when the cluster is bound.

Select an AZ from the AZ drop-down list.
Select a CCE cluster that can be bound in the AZ from the Cluster drop-down list.
Click OK.
Click Add Cluster.
Select another AZ from the AZ drop-down list.
Select a CCE cluster that can be bound in the AZ from the Cluster drop-down list.
Click OK.

Select the cluster to be bound from the Cluster drop-down list.
Select the namespace to be bound to the CCE cluster from the Namespace drop-down list.
When you create and deploy a component in an environment bound with a CCE cluster, the namespace bound to the CCE cluster is specified. During component creation and deployment, if the current environment is used to build component images, this namespace is used to isolate build data by default. It is also used to isolate created component instances by default.

After binding a cluster, you can bind a new namespace to the cluster based on service requirements. For details, see Binding a Namespace.
Click OK.

If the Sermant Injector plug-in has been installed for the selected cluster, manage the ServiceComb engine or registry/configuration center associated with the installed Sermant Injector plug-in. Otherwise, the Sermant Injector plug-in will be unavailable in this environment. For details, see Managing Basic Resources.

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?