Connect an existing cluster
KubeNest does not currently support connecting an existing Kubernetes cluster — EKS, GKE, AKS, kubeadm, or an already-running k3s — to a control plane.
Do not run kubenest cluster connect: that command is not implemented. Creating a manual cluster
record in the console records metadata only; the record has no agent behind it, so it never connects.
What works today
Every cluster KubeNest manages comes from the platform installer, on hosts you supply. The first install creates the control plane and registers itself to it; further clusters register to the same control plane through the same API path:
# On the first cluster: platform bundle and control plane together.
kubenest platform install --control-plane --bundle 1.1 --name mgmt ...
# On each further cluster, from a logged-in CLI.
kubenest platform install --bundle 1.1 --name client-a ...The installer establishes a new K3s platform and deliberately refuses hosts that already run Kubernetes. See Install the platform for the supported new-host path and Quickstart for the two commands end to end.
Bringing an existing cluster under management would mean adopting the ingress, CSI and certificate manager already installed on it — the untested component combination the bundle exists to eliminate. It will be documented here only once the CLI can install the bundle-pinned agent through a supported transport and verify its real control-plane heartbeat.
Next: Install the platform · Day 2