Cluster Management Overview
Efficient, stable operation of containerized applications relies on proper management of CCE standard or Turbo clusters. CCE standard and Turbo clusters offer comprehensive management capabilities, including cluster configuration, resource scheduling, security control, and lifecycle management. Configure, optimize, and manage clusters according to your service needs to ensure stable, high-performance operation of containerized applications.
Cluster Configurations and Resource Management
Cluster configuration and resource management enable flexible parameter adjustments and dynamic resource allocation. This allows you to optimize cluster performance and efficiently utilize resources based on service requirements. For details, see Table 1.
Feature |
Description |
---|---|
Cluster configuration parameters define node behavior, resource allocation, communication rules, and scaling policies in a distributed system. They affect the cluster's performance, stability, scalability, and fault tolerance. You can customize the core components of a CCE standard or Turbo cluster by adjusting these parameter settings. |
|
Overload control dynamically limits concurrent external requests based on the resource pressure of the master node, ensuring the stability and reliability of both the master node and the cluster. In a CCE standard or Turbo cluster, you can enable cluster overload control, monitor cluster overload, and configure overload alarms to mitigate the risk of cluster overload. |
|
A cluster scale specifies the maximum number of nodes a cluster can manage. If the current cluster scale does not meet your requirements, you can change it to handle changing workloads. |
Cluster Security and Access Control
A security group is a virtual firewall that controls inbound and outbound network traffic for a cluster. You can modify the default security group rules of cluster nodes to enhance network security based on your needs. For details, see Changing the Default Security Group of a Node.
Cluster Lifecycle Management
Managing CCE standard and Turbo clusters varies by billing mode. For details, see Table 2.
Billing Mode |
Operation |
Description |
---|---|---|
Pay-per-use |
Hibernate unused clusters to save costs. Quickly wake them up to restore services when needed. |
|
Changing the Billing Mode of a Cluster from Pay-per-Use to Yearly/Monthly |
CCE standard and Turbo clusters support both pay-per-use and yearly/monthly billing modes. The billing mode of a cluster can be changed from pay-per-use to yearly/monthly. |
|
Enable this function to protect critical clusters against accidental deletion through the console or APIs. |
||
Delete an unused cluster to release resources. |
||
Yearly/Monthly |
Renew a yearly/monthly cluster before it expires. |
|
Unsubscribing From or Releasing a Yearly/Monthly-Billed Cluster |
A yearly/monthly cluster cannot be directly deleted. Instead, unsubscribe from it before expiration to release resources. |
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.