Cluster Access

Objective

This guide explains how to use Cluster Access on Ruk-Com Cloud PaaS, with ordered procedures and practical verification points.

Before you begin

• Sign in with an account permitted to manage the relevant environment.
• Confirm the target environment, region and resources before saving changes.
• Create a backup or rollback plan before changing a production system.

After theInstall clusterThere are several ways to access the cluster to start managing it:

• Kubernetes Dashboard
• kubectl client

Kubernetes dashboard

1. The post-installation popup will provide all the necessary information to connect to the Kubernetes dashboard – links and access tokens.

The same information is also made available through email notifications.

2. Go to the link, select the Token option and paste the desired value.

Tips :
It is also possible to log in with the kubeconfig file, however you will need to install kubectl and set the correct content (look insectionbelow)

3. If you have lost your email address along with your Kubernetes cluster access token, you can view it by executing the following command on the master node (e.g. viaWeb SSH):

kubectl -n kube-system describe secret $(kubectl -n kube-system get secret | grep fulladmin | awk '{print $1}') | grep 'token:' | sed -e's/token:\| //g'

You can now access the Kubernetes dashboard again.

Kubectl Client

KubectlA command-line tool to control Kubernetes clusters, Ruk-Com is automatically installed on all master nodes during environment creation. You can start working with your cluster using kubectl right away by simply connecting to the desired node viaover SSH

1. Followinstallation stepsto usekubectlon the machine, then run the command to establish the remote connection.

kubectl config set-cluster jelastic --server={api-endpoint} && \
kubectl config set-context jelastic --cluster=jelastic && \
kubectl config set-credentials user --token={token} && \
kubectl config set-context jelastic --user=user && \
kubectl config use-context jelastic

replace position{api-endpoint}and{token}with Remote API URL and access token respectively

Tips :
If you did not enable the Remote API during installation, this can be done via the add-on available for the master node in the Ruk-Com dashboard.

2. You can verify that kubectl can access the cluster with the following command:

kubectl get pods

You should see information about the pod in the default namespace.