Cluster Management
A cluster is the core object Kuboard manages. This section walks through the full lifecycle — connecting the first Kubernetes cluster, day-to-day maintenance of the connection and cache, and moving resources between clusters.
Quick Navigation
| Section | Content | When to Read |
|---|---|---|
| Import Cluster | Import a new cluster via kubeconfig or ServiceAccount | First-time connection to a K8s cluster |
| Edit Cluster | Change cluster name, description, connection parameters and cache strategy | Adjust settings on an existing cluster |
| Sync Status | Inspect full and incremental sync progress, error logs | Troubleshoot stuck or failing syncs |
| Resource Export and Import | Bulk import/export K8s resources (YAML) between clusters | Cross-cluster migration and DR |
Recommended Reading Order
- First connection — start with Import Cluster and fill in the apiserver address and credentials;
- Day-to-day maintenance — tune cache strategy and defaults from Edit Cluster;
- Troubleshooting — when something looks wrong in the cluster list, start at Sync Status to separate sync-pipeline issues from connection problems;
- Cross-cluster moves — use Resource Export and Import for bulk migration.
Where to go next
After Import Cluster, continue to the Workloads section to deploy your first application. In a multi-cluster setup, auth.clusterIds and auth.clusterNames (from useAuthStore) determine which clusters appear in the left sidebar.
