Help Center/ ServiceStage/ User Guide/ Environment Management/ Managing Basic Resources in the Environment/ Managing Cluster Resources/ Binding a Cluster/ Binding a CCE Cluster
Updated on 2025-09-26 GMT+08:00
View PDF
Share

Binding a CCE Cluster

Before creating a component based on a container in the Kubernetes or VM + Kubernetes environment, bind a cluster to the environment.

CCE clusters can be bound to a Kubernetes or VM + Kubernetes environment.

Restrictions

  • Only CCE Turbo clusters or CCE standard clusters can be bound to the environment. For details about CCE cluster types, see Cluster Types.

    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 configure SNAT rules for a cluster, see Accessing the Internet from a Container.

  • If IPv6 is enabled for the VPC where the target environment is located, 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?

Prerequisites

  • You have created an environment. For details, see:
  • If you want to bind a CCE cluster, a CCE cluster in the Running state has been created, and the CCE cluster and environment must be in the same VPC.
    • For details about how to create a CCE cluster, see Buying a CCE Standard/Turbo Cluster. Create a CCE Turbo or CCE Standard cluster based on your service requirements.
      • For a Kubernetes HA environment, create a CCE cluster for each AZ.
      • For a Kubernetes non-HA environment or a VM + Kubernetes environment, create a CCE cluster.
    • For details about how to add a node to the CCE cluster, see Creating a Node.
      • CCE clusters support Elastic Cloud Server (VM) and BMS nodes.
      • For details about the OSs supported by CCE cluster nodes, see Node OSs.
      • CCE cluster nodes support Docker and Containerd container engines. For details about the mapping between node OSs and container engines, see Container Engines.

Procedure

  1. Log in to ServiceStage.
  2. Choose Environment Management. The Environment Management page is displayed.
  3. Click the target environment. The Overview page is displayed.
  4. Choose Clusters from Compute.

  5. Click Bind now.

    Table 1 Binding a cluster

    HA Environment or Not

    How to Bind

    Yes

    Only CCE clusters can be bound.

    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.

    1. Select an AZ from the AZ drop-down list.
    2. Select a CCE cluster that can be bound in the AZ from the Cluster drop-down list.
    3. Click OK.
    4. Click Add Cluster.
    5. Select another AZ from the AZ drop-down list.
    6. Select a CCE cluster that can be bound in the AZ from the Cluster drop-down list.
    7. Click OK.

      After the CCE cluster is bound, the cluster-created namespace default, existing namespaces, and new user-created namespaces are automatically bound. For details, see Managing Namespaces.

    No
    1. Select CCE cluster for Cluster Source.
    2. Select the cluster to be bound from the Cluster drop-down list.
    3. (Optional) Select the namespace to be bound to the CCE cluster from the Namespace drop-down list.
      • If no namespace is selected, after the CCE cluster is bound, the cluster-created namespace default, existing namespaces, and new user-created namespaces are automatically bound.
      • If a namespace is selected, the selected namespace is bound after the CCE cluster is bound. For details, see Managing Namespaces.
    4. Click OK.

    If you have performed Installing Sermant Injector for the cluster, manage the ServiceComb engine or registry/configuration center associated with the installed Sermant Injector plug-in in the environment. 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.

Follow-up Operations

  • On the Overview page, click the Node List tab to view details about each node in the CCE cluster.
  • On the Overview page, click the Namespace tab to manage cluster namespaces by referring to Managing Namespaces.
  • On the Overview page, click the ConfigMaps tab to manage cluster configuration items by referring to Managing Configuration Items.
  • On the Overview page, click the Secrets tab to manage cluster secrets by referring to Managing Secrets.
  • On the Overview page, click View Resource Details to view cluster details on the CCE console.
  • On the Plug-in Management page, you can manage cluster plug-ins by referring to Managing Plug-ins.
  • If the cluster bound to the environment is no longer used, unbind the cluster by referring to Unbinding a Cluster.
Parent topic: Binding a Cluster