The platform supports importing Google GKE clusters.
The Kubernetes version and components on the cluster meet the version requirements for importing public cloud clusters.
Ensure the cluster type is a standard cluster and the account has permissions to maintain the control plane. Autopilot clusters are not currently supported.
The image repository must support HTTPS access and provide a valid TLS certificate authenticated by a public certification authority.
To comply with GKE security standards, the following steps must be performed using Cloud Shell.
Ensure network connectivity with Google.
Access the Clusters page in the Kubernetes Engine feature; find the cluster to be imported, click on cluster details, and select the Connect button.
In the popup dialog, copy the command for configuring kubectl command-line access permissions and click the Run in Cloud Shell button.
Wait for Cloud Shell to be ready, clear the command line, paste the content copied in the previous step, and execute it.
The environment is now ready. All subsequent commands executed in the importing cluster environment for steps such as Obtaining Cluster Information and Importing Cluster should be executed in Cloud Shell.
Access the Clusters page in the Kubernetes Engine feature and click to enter the details page of the target cluster.
The API Server address can be found in the External endpoints section.
To obtain the CA certificate, use one of the following methods in Cloud Shell:
Method A: Get the CA certificate from your kubeconfig:
Method B: Get the CA certificate directly from the cluster:
Note: The certificate must be Base64-decoded before pasting into the import form.
The KubeConfig file of public cloud clusters cannot be directly used for importing clusters.
Please refer to the FAQ How to obtain cluster information? to obtain the target cluster token.
In the left navigation bar, click Clusters > Clusters.
Click Manage Cluster > Import Cluster.
Configure the relevant parameters according to the following instructions.
| Parameter | Description |
|---|---|
| Image Repository | Repository for storing platform component images required by the cluster. - Platform Default: Image repository configured during global deployment. - Private Repository: Pre-built repository storing platform required components. Requires input of Private Image Repository Address, Port, Username, and Password for accessing the image repository. - Public Repository: Use public image repository services on the internet. Before use, you must first refer to Update Public Repository Cloud Credentials to obtain repository authentication permissions. |
| Cluster Information | Cluster Information: Includes the target cluster token and the API Server address and CA certificate of the target cluster. Cluster Address: The access address where the target cluster exposes the API Server for platform access to the cluster's API Server. CA Certificate: CA certificate of the target cluster. Note: When manually inputting, you need to enter the Base64 decoded certificate. Authentication Method: Authentication method for the target cluster, requires using the token (Token) with cluster management permissions created in the previous step for authentication. |
Click Check Connectivity to verify network connectivity with the target cluster and automatically identify the cluster type, which will be displayed as a badge in the top-right corner of the form.
After connectivity check passes, click Import and confirm.
Ensure network connectivity between the global cluster and the imported cluster. See Network Configuration for Imported Clusters.
After importing the cluster, if you need to use Ingress and storage-related features, please refer to Google GKE Ingress Controller Configuration and Google GKE Storage Configuration.
Adding nodes through the platform interface is not supported. Please contact the cluster provider to add nodes.
Kubernetes Certificates: All imported clusters only support viewing APIServer certificate information in the platform certificate management interface. Other Kubernetes certificates cannot be viewed and automatic rotation is not supported.
Platform Component Certificates: All imported clusters can view platform component certificate information in the platform certificate management interface and support automatic rotation.