Skip to content

Access Clusters

Clusters integrated or created using the DCE 5.0 Container Management platform can be accessed not only through the UI interface but also in two other ways for access control:

  • Access online via CloudShell
  • Access via kubectl after downloading the cluster certificate

Note

When accessing the cluster, the user should have Cluster Admin permission or higher.

Access via CloudShell

  1. Enter Clusters page, select the cluster you want to access via CloudShell, click the ... icon on the right, and then click Console from the dropdown list.

    screen

  2. Run kubectl get node command in the Console to verify the connectivity between CloudShell and the cluster. If the console returns node information of the cluster, you can access and manage the cluster through CloudShell.

Access via kubectl

If you want to access and manage remote clusters from a local node, make sure you have met these prerequisites:

  • Your local node and the cloud cluster are in a connected network.
  • The cluster certificate has been downloaded to the local node.
  • The kubectl tool has been installed on the local node. For detailed installation guides, see Installing tools.

If everything is in place, follow these steps to access a cloud cluster from your local environment.

  1. Enter Clusters page, find your target cluster, click ... on the right, and select Download kubeconfig in the drop-down list.

    Enter the page of downloading certificates

  2. Set the Kubeconfig period and click Download .

    Download certificates

  3. Open the downloaded certificate and copy its content to the config file of the local node.

    By default, the kubectl tool will look for a file named config in the $HOME/.kube directory on the local node. This file stores access credentials of clusters. Kubectl can access the cluster with that configuration file.

  4. Run the following command on the local node to verify its connectivity with the cluster:

    kubectl get pod -n default

    An expected output is as follows:

    NAME                            READY   STATUS      RESTARTS    AGE
dao-2048-2048-58c7f7fc5-mq7h4   1/1     Running     0           30h

Now you can access and manage the cluster locally with kubectl.

Comments