Overview
After a cluster reachesCREATE_COMPLETE status, you connect to it using kubectl
and the cluster’s kubeconfig file. Xloud K8SaaS generates a unique certificate authority
per cluster and embeds the cluster API server endpoint, CA certificate, and user
credentials into the kubeconfig. This page covers downloading credentials, configuring
kubectl, and verifying connectivity.
Prerequisites
- A cluster in
CREATE_COMPLETEstatus kubectlinstalled locally (install guide)- Network access from your machine to the cluster API server (port 6443)
Download Cluster Credentials
- Dashboard
- CLI
Navigate to the cluster
Log in to the Xloud Dashboard (
https://connect.<your-domain>) and navigate to
Project → Containers → Clusters. Click your cluster name.Download kubeconfig
On the cluster detail page, click Download kubeconfig. Save the file
(e.g.,
prod-cluster-01-kubeconfig.yaml) to your machine.Configure kubectl
Set the
KUBECONFIG environment variable to point to the downloaded file:Set kubeconfig
Manage Multiple Cluster Contexts
If you access multiple clusters, usekubectl contexts to switch between them.
View all configured contexts
Switch to a specific cluster context
Merge multiple kubeconfigs
API Server Endpoint
The cluster API server endpoint is accessible via the master load balancer floating IP or directly via the master node floating IP (for single-master clusters).Show API server endpoint
The API server listens on port 6443 (HTTPS). Ensure your workstation’s network allows
outbound TCP to port 6443 on the cluster API server IP.
Validation
- Dashboard
- CLI
Navigate to Project → Containers → Clusters and click your cluster. Verify:
- Health Status:
HEALTHY - All listed nodes show
STATUS: Ready
Cluster is healthy and all nodes are ready to accept workloads.
Next Steps
Node Groups
Create specialized node pools and schedule workloads to specific groups.
Scale Cluster
Add or remove worker nodes from your cluster.
Cluster Upgrades
Upgrade your cluster to a newer Kubernetes version.
Troubleshooting
Resolve kubectl connectivity and node health issues.