The four parts
The division that matters: the plane decides, your account holds. Your clusters, their build state, and the keys that protect it live in your AWS account. Revoke the build role and Kubox stops managing them. It never held a copy.
The normal path
Four commands take you from nothing to a running cluster.1
Sign in
kubox login.2
Create the boundary in your AWS account
kubox cloud bootstrap.3
Connect the account
kubox cloud connect.4
Create a cluster
kubox cluster create.5
Reach it with kubectl
kubox cluster connect.From here it is an ordinary Kubernetes cluster — your existing manifests, operators, and tools work unchanged. Kubox provisions the cluster; deploying your application is still your job.The direct path
kubox admin drives a cloud or a cluster from your machine with the credentials you already hold, with no management plane involved:
admin when the normal path cannot help:
- a cluster no plane manages
- the first plane, before one exists
- a failure you need to get underneath
Both paths produce the same cluster. The difference is who holds the credentials and who tracks the result.
Where to go next
Management plane
What a plane owns, and when you need your own.
Cloud accounts
The trusted boundary, and what Kubox can and cannot do in your account.
CLI reference
Every command, option, and consequence.