Download the cluster’s connection configuration from the service page and use it with your Kubernetes client. The kubeconfig contains credentials that can administer the cluster, so handle it as a secret.

Find the intended cluster

Open the service’s Information tab in the Blesta client area. Confirm the service name and cluster state, then find the API endpoint in the connection information. Choose View connection details, then locate Download kubeconfig.

Enable Client: Kubeconfig download on the offering. A suspended service or unavailable management feature can prevent a download. Do not use a provider token or a guessed download address to bypass a refused control.

Download and select its context

1. Choose Download kubeconfig for the intended service.
2. Save the file privately on the administration device. Do not paste its contents into a ticket, public repository or screenshot.
3. Import or select that file in your Kubernetes client, such as kubectl or a client that supports kubeconfig. Review the context name and API endpoint before running an action so you do not target another cluster already configured on that device.
4. Check the node list using your normal Kubernetes administration process. A successful download is not itself a test of endpoint reachability or workload health.

DigitalOcean’s cluster connection guide explains kubeconfig authentication. Downloaded credentials can expire; this module does not make a downloaded file permanent or automatically refresh a copy on your device. Obtain a fresh file through the same authorised control when required.

If access does not work

For a missing or refused button, review activation/suspension state and the kubeconfig feature switch. For a failed download, review the selected provider account and the exact redacted result; account-read success does not prove this separate permission.

If the file downloads but your client cannot connect, check that you selected the intended context, that the credentials are current and that the administration device can reach the cluster endpoint. Do not turn off certificate validation simply to clear a connection error.

Never attach the kubeconfig, credential fields, API token or a screenshot exposing cluster credentials.

See the PD DigitalOcean Kubernetes Blesta guide for related setup, or explore PD DigitalOcean Kubernetes.