Cluster Access

Kubernetes Cluster Access

After a Kubernetes cluster is installed successfully, it can be managed in two primary ways: through the web-based Kubernetes Dashboard or through the kubectl command-line client. The platform provides the access token and connection information required for both methods.
Kubernetes Dashboard Use the web interface with an access token, or authenticate with kubeconfig when configured.
kubectl Client Manage Kubernetes resources from the command line locally or directly from a cluster master node.
On this page

Access via Kubernetes Dashboard

1Get the dashboard URL and token

After cluster installation completes, the success pop-up displays the Kubernetes Dashboard link together with the access token required to sign in. The same access information is also sent in the installation email notification.

Kubernetes installation success frame
The installation success message provides the Kubernetes Dashboard link and access token.

2Sign in with the token

Open the Kubernetes Dashboard link, select the Token authentication option, paste the provided access token, and sign in.

Kubernetes Dashboard token access
Select Token authentication and enter the access token.
It is also possible to log in using a kubeconfig file. To use that approach, install kubectl locally and configure the appropriate Kubernetes context.

Recover a Lost Access Token

If the installation email or original access token is no longer available, retrieve the token from a Kubernetes master node, for example through Web 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'
View Kubernetes access token using Web SSH
Retrieve the Kubernetes Dashboard token from a master node.
Security: Treat the Kubernetes access token as a credential. Do not publish it, store it in public repositories, or send it through insecure communication channels.

Access via kubectl

kubectl is the standard Kubernetes command-line client. The platform automatically installs it on all Kubernetes master nodes, so cluster management can begin immediately after connecting to a master node over SSH.

Master Node Access Connect to a Kubernetes master node over SSH and use the pre-installed kubectl client.
Local Computer Access Install kubectl on your workstation and configure the Remote API endpoint and token.

For local access, install kubectl on your computer and configure a cluster, user, and context using the Remote API URL and cluster access token.

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 {api-endpoint} with the Kubernetes Remote API URL and {token} with the access token.

Enable Remote API Access

If Remote API access was not enabled during the initial Kubernetes package installation, it can be enabled later through the built-in add-on on the master node.

1Open master-node add-ons

In the platform dashboard, open the Kubernetes master node and click Add-Ons.

2Enable Remote API

Open Kubernetes Cluster Configuration and select the Remote API option.

Enable Remote API for Kubernetes cluster
Remote API access can be enabled through the Kubernetes Cluster Configuration add-on.

Verify kubectl Connection

After the local kubectl context is configured, verify connectivity by requesting the pods in the default namespace.

kubectl get pods

If access is configured correctly, the command returns information about pods running in the default namespace.

kubectl access to Kubernetes cluster
Successful kubectl access displays the pods in the Kubernetes cluster.
Result: Kubernetes can be managed either through the web dashboard or with kubectl. For remote command-line management, make sure Remote API access is enabled and protect the API endpoint and token carefully.

What’s next?