A200161411/cloud-container-engine
1
0
Fork 0
forked from docs/cloud-container-engine
Code Pull Requests Activity
cloud-container-engine/umn/source/clusters/managing_a_cluster/cluster_configuration_management.rst

34 KiB
Raw Blame History

original_name

cce_10_0213.html

Cluster Configuration Management

Scenario

CCE allows you to manage cluster parameters, through which you can let core components work under your very requirements.

Constraints

This function is supported only in clusters of v1.15 and later. It is not displayed for versions earlier than v1.15.

Procedure

  1. Log in to the CCE console. In the navigation pane, choose Clusters.

  2. Click image1 next to the target cluster.

  3. On the Manage Components page on the right, change the values of the Kubernetes parameters listed in the following table.

    Table 1 kube-apiserver parameters
    Parameter Description Value
    default-not-ready-toleration-seconds

    Tolerance time when a node is in the NotReady state.

    By default, this tolerance is added to each pod.

    		 Default: 300s
    default-unreachable-toleration-seconds

    Tolerance time when a node is in the unreachable state.

    By default, this tolerance is added to each pod.

    		 Default: 300s
    max-mutating-requests-inflight

    Maximum number of concurrent mutating requests. When the value of this parameter is exceeded, the server rejects requests.

    The value 0 indicates no limitation. This parameter is related to the cluster scale. You are advised not to change the value.

    Manual configuration is no longer supported since cluster v1.21. The value is automatically specified based on the cluster scale.

    • 200 for clusters with 50 or 200 nodes
    • 500 for clusters with 1,000 nodes
    • 1000 for clusters with 2,000 nodes
    max-requests-inflight

    Maximum number of concurrent non-mutating requests. When the value of this parameter is exceeded, the server rejects requests.

    The value 0 indicates no limitation. This parameter is related to the cluster scale. You are advised not to change the value.

    Manual configuration is no longer supported since cluster v1.21. The value is automatically specified based on the cluster scale.

    • 400 for clusters with 50 or 200 nodes
    • 1000 for clusters with 1,000 nodes
    • 2000 for clusters with 2,000 nodes
    service-node-port-range NodePort port range. After changing the value, go to the security group page and change the TCP/UDP port range of node security groups 30000 to 32767. Otherwise, ports other than the default port cannot be accessed externally.

    Default:

    30000-32767

    Value range:

    Min > 20105

    Max < 32768
    support-overload

    Cluster overload control. If enabled, concurrent requests are dynamically controlled based on the resource pressure of master nodes to keep them and the cluster available.

    This parameter is supported only by clusters of v1.23 or later.
    • false: Overload control is disabled.
    • true: Overload control is enabled.
    Table 2 kube-scheduler parameters
    Parameter Description Value
    kube-api-qps Query per second (QPS) to use while talking with kube-apiserver.
    • If the number of nodes in a cluster is less than 1000, the default value is 100.
    • If a cluster contains 1000 or more nodes, the default value is 200.
    kube-api-burst Burst to use while talking with kube-apiserver.
    • If the number of nodes in a cluster is less than 1000, the default value is 100.
    • If a cluster contains 1000 or more nodes, the default value is 200.
    Table 3 kube-controller-manager parameters
    Parameter Description Value
    concurrent-deployment-syncs Number of Deployments that are allowed to synchronize concurrently. Default: 5
    concurrent-endpoint-syncs Number of endpoints that are allowed to synchronize concurrently. Default: 5
    concurrent-gc-syncs Number of garbage collector workers that are allowed to synchronize concurrently. Default: 20
    concurrent-job-syncs Number of jobs that can be synchronized at the same time. Default: 5
    concurrent-namespace-syncs Number of namespaces that are allowed to synchronize concurrently. Default: 10
    concurrent-replicaset-syncs Number of ReplicaSets that are allowed to synchronize concurrently. Default: 5
    concurrent-resource-quota-syncs Number of resource quotas that are allowed to synchronize concurrently. Default: 5
    concurrent-service-syncs Number of Services that are allowed to synchronize concurrently. Default: 10
    concurrent-serviceaccount-token-syncs Number of service account tokens that are allowed to synchronize concurrently. Default: 5
    concurrent-ttl-after-finished-syncs Number of TTL-after-finished controller workers that are allowed to synchronize concurrently. Default: 5
    concurrent-rc-syncs

    Number of replication controllers that are allowed to synchronize concurrently.

    Note

    This parameter is used only in clusters of v1.21 to v1.23. In clusters of v1.25 and later, this parameter is deprecated (officially deprecated from v1.25.3-r0 on).

    		 Default: 5
    horizontal-pod-autoscaler-sync-period How often HPA audits metrics in a cluster. Default: 15 seconds
    kube-api-qps Query per second (QPS) to use while talking with kube-apiserver.
    • If the number of nodes in a cluster is less than 1000, the default value is 100.
    • If a cluster contains 1000 or more nodes, the default value is 200.
    kube-api-burst Burst to use while talking with kube-apiserver.
    • If the number of nodes in a cluster is less than 1000, the default value is 100.
    • If a cluster contains 1000 or more nodes, the default value is 200.
    terminated-pod-gc-threshold

    Number of terminated pods that can exist before the terminated pod garbage collector starts deleting terminated pods.

    If <= 0, the terminated pod garbage collector is disabled.

    		 Default: 1000
    Table 4 eni parameters (supported only by CCE Turbo clusters)
    Parameter Description Value
    nic-minimum-target Minimum number of ENIs bound to a node at the cluster level Default: 10
    nic-maximum-target Maximum number of ENIs pre-bound to a node at the cluster level Default: 0
    nic-warm-target Number of ENIs pre-bound to a node at the cluster level Default: 2
    nic-max-above-warm-target Reclaim number of ENIs pre-bound to a node at the cluster level Default: 2
    prebound-subeni-percentage

    Low threshold of the number of bound ENIs: High threshold of the number of bound ENIs

    Note

    This parameter is being discarded. Use the dynamic pre-binding parameters of the other four ENIs.

    		 Default: 0:0
    Table 5 Extended controller configuration parameters (supported only by clusters of v1.21 and later)
    Parameter Description Value
    enable-resource-quota

    Whether to automatically create a resource quota object when creating a namespace.

    • false: no auto creation
    • true: auto creation enabled For details about the resource quota defaults, see Setting a Resource Quota <cce_10_0287>.
    		 Default: false

  4. Click OK.

References