Platform Center
Home / Platform management / Clusters / Clusters / Cluster Parameter Requirements

Cluster Parameter Requirements

This section describes the parameters that you need to meet when you use a cluster managed by the platform.

self-managed cluster

Version Requirements

Kubernetes 版本 Istio 版本
1.27.16-1 1.22.4
1.28.13 1.22.4
1.29.8 1.22.4
1.30.4 1.22.4

Node parameter requirements

Prepare and check the nodes to be added to the cluster based on the Node Availability Check Reference Table(/en/platform-usermanual/clusterall/1cluster/10node/1nodeview/#nodecheck01). Make sure that all the conditions are met, otherwise the cluster deployment may fail.

Manage clusters

standard Kubernetes cluster

Version Requirements

|Source|   Kubernetes version |      Istio version |  Runtime Component | 
|---| ------ |  -------- | -------- | 
|**Standard Kubernetes Cluster**| 1.27.x | 1.22.4 |  -  |
|**Standard Kubernetes Cluster**| 1.28.x |  1.22.4 |  -  | 
|**Standard Kubernetes Cluster**|1.29.x |  1.22.4 |   -  |
|**Standard Kubernetes Cluster**| 1.30.X |  1.22.4 |  -  |

Network Requirements:

Access Cluster: Ensure that the global can access the Connected Cluster, and open the ‘11780’, ‘11781’ ports of all hosts in the connected cluster.

Register Cluster: Make sure that the registered cluster has access to the global cluster.

Image Repository Requirements: You need to prepare an image repository that contains platform component images, which can be a built-in image repository in the global cluster, a third-party image repository, or a public repository.

Component Parameter Requirements

<table>
    <tr>
        <th>parameters</th>
        <th>Required parameters</th>
        <th>Scope of influence</th>
    </tr>
    <tr>
        <td rowspan="12">kube-apiserver</td>
        <td>allow-privileged=true</td>
        <td>Some components need to be run in privileged mode. </td>
    </tr>
    <tr>
        <td>audit-log-format=json</td>
        <td rowspan="2" > affects the audit function. audit-log-format must be json, and audit-log-path can be configured with other values. </td>
    </tr>
    <tr>
        <td>audit-log-path=/etc/kubernetes/audit/audit.log</td>
    </tr>
    <tr>
        <td>feature-gates=Ephemeralcontainers=true</td>
        <td>Affects the kubectl debug feature. </td>
    </tr>
    <tr>
        <td>authorization-mode=node,RBAC</td>
        <td>Permissions. </td>
    </tr>
    <tr>
        <td>proxy-client-cert-file=/etc/kubernetes/pki/front-proxy-client.crt</td>
        <td rowspan="7", > lack of configuration will prevent the normal use of APIService, resulting in the failure of functions such as OperatorHub and PrometheusAdapter. Other values can be configured for proxy-client-cert-file, proxy-client-key-file, requestheader-allowed-names, and proxy-client-key-file. </td>
    </tr>
    <tr>
        <td>proxy-client-key-file=/etc/kubernetes/pki/front-proxy-client.key</td>
    </tr>
    <tr>
        <td>requestheader-allowed-names=front-proxy-client</td>
    </tr>
    <tr>
        <td>requestheader-client-ca-file=/etc/kubernetes/pki/front-proxy-ca.crt</td>
    </tr>
    <tr>
        <td>requestheader-extra-headers-prefix=X-Remote-Extra</td>
    </tr>
    <tr>
        <td>requestheader-group-headers=X-Remote-Group</td>
    </tr>
    <tr>
        <td>requestheader-username-headers=X-Remote-User</td>
    </tr>
    <tr>
        <td rowspan="2">kube-scheduler</td>
        <td>feature-gates=EphemeralContainers=true</td>
        <td>Affects the kubectl debug feature. </td>
    </tr>
    <tr>
        <td>bind-address=0.0.0.0</td>
        <td>Some monitoring metrics that affect the cluster. </td>
    </tr>
    <tr>
        <td rowspan="3">kube-controller-manager</td>
        <td>controllers=*,bootstrapsigner,tokencleaner</td>
        <td>It is recommended to enable all controller functions, otherwise the corresponding functions may be missing. </td>
    </tr>
    <tr>
        <td>feature-gates=EphemeralContainers=true</td>
        <td>Affects the kubectl debug feature. </td>
    </tr>
    <tr>
        <td>bind-address=0.0.0.0</td>
        <td>Some monitoring metrics that affect the cluster. </td>
    </tr>

**kubectl configuration file requirements**:

In the /var/lib/kubelet/config.yaml file, you need to meet the following parameters:

1. To ensure that the component is accessed properly, you need to add key-value pairs: 'clusterDomain': 'cluster.local'.

2. The parameters required for monitoring component authentication are as follows:

    ```
    authentication:
        webhook:
            enabled: true
        x509:
            clientCAFile: /etc/kubernetes/pki/ca.crt
    authorization:
        mode: Webhook
    ```

public cloud cluster

Version Requirements

|Source|   Kubernetes version |      Istio version |  Runtime Component | 
|---| ------ |  -------- | -------- | 
| **Amazon EKS Clusters** | 1.27<br>1.28<br>1.29<br>1.30 |  1.22.4| Containerd  |   
| **Azure AKS Clusters**| 1.27<br>1.28<br>1.29<br>1.30 | 1.22.4|  Containerd |  
| **华为云 CCE Clusters（Public Cloud）** |  1.25.x<br>1.27.x | 1.22.4 |Docker<br>Containerd |
| **Google GKE Clusters** | 1.29<br>1.30 | 1.20|   Containerd  |
| **Openshift Clusters** |  1.27<br>1.28<br>1.29<br>1.30  | 1.22.4|   Containerd  |
| **AliCloud ACK Clusters** | 1.27<br>1.28<br>1.29<br>1.30 | 1.22.4|   Containerd  |
| **Tencent TKE Clusters** | 1.27<br>1.28<br>1.29<br>1.30  | 1.22.4|   Containerd  |

Network Requirements:

Access Cluster: Ensure that the global can access the Connected Cluster, and open the ‘11780’, ‘11781’ ports of all hosts in the connected cluster.

Register Cluster: Make sure that the registered cluster has access to the global cluster.

Image Repository Requirements: You need to prepare an image repository that contains platform component images, which can be a built-in image repository in the global cluster, a third-party image repository, or a public repository.

Create a public cloud cluster

Version Requirements

Creating a Public Cloud Cluster

The supported versions of Kubernetes for public cloud clusters can be found on the corresponding creation page, and a cross-reference between Kubernetes and Istio versions can be found in the version requirements section of the standard Kubernetes cluster.