Dashboard

Accessing the Settings

1. Log in to the CCE console and click the cluster name to access the cluster console.
2. In the navigation pane, choose Settings and click the Dashboard tab.

Cluster Information

• ID: uniquely identifies a cluster resource. It is automatically generated after a cluster is created and can be used in scenarios such as API calling.
• Current Name: After a cluster is created, you can click to change its name.
• Original Name: specifies a cluster's original name after its current name is changed. The current name of a cluster must be unique.
• Status: specifies the status of a cluster. For details, see Cluster Lifecycle.
• Type: specifies whether a cluster is a CCE standard cluster or a CCE Turbo cluster. For details about the differences between CCE standard and CCE Turbo clusters, see Comparison Between Cluster Types.
• Created On: specifies the time when a cluster was created. You will be billed based on the creation time of clusters.

Cluster Settings

• Cluster Scale: specifies how many nodes a cluster can manage at most. You can change the cluster scale as needed. For details, see Changing a Cluster Scale.
• Cluster Version | Patch Version: specifies the Kubernetes version and CCE patch version of a cluster.
• Network Model: specifies the network model of a cluster, which cannot be changed. For details about network models, see Container Network.
• Billing Mode: specifies the billing mode of a cluster.
• Enterprise Project: specifies the enterprise project to which a cluster belongs.
• Operation Protection: After this function is enabled, you need to confirm operations by using the virtual MFA device, SMS messages, or emails. You can go to the IAM console, choose Security Settings > Critical Operations, and enable the protection functions.
• Resource Tag: You can add resource tags to classify resources.
• Cluster Description: specifies the description that you entered for a cluster. A maximum of 200 characters are allowed.
• Secret Encryption: You can encrypt Kubernetes secrets stored in CCE using envelope encryption with KMS keys. For details, see Using KMS to Encrypt Secrets.
• Global OBS Access Secret (paas.longaksk): If you have created a global access key while using OBS volumes in a cluster, the system will create a secret called paas.longaksk in the kube-system namespace of the cluster. This secret is used to store the global AK and SK.

  The global access key (paas.longaksk) is used by project. Once a global access key is used, it is automatically created for each cluster within the same project. However, this can lead to security and management complexities. Therefore, it is not recommended that you use global access secrets. To disable global access keys, check whether the cluster uses global access keys. For details, see What Is an OBS Global Access Key and How Do I Check Whether a Global Access Key Is Used in a Cluster?

• Cluster Deletion Protection: A measure taken to prevent accidental deletion of clusters through the console or APIs. After this function is enabled, you will not be able to delete or unsubscribe from clusters.

Master Node AZs

Installed Add-ons