Skip to main content
Build the cluster a plane runs on, then install the plane into it

Synopsis

The two halves of standing up a management plane, from one document.
  1. compile the PlaneDeployment into a cluster document
  2. kubox admin create that cluster
  3. kubox admin install the plane into it
It calls the same code those commands call rather than reimplementing either: a second way of building a cluster is a second set of steps to keep in agreement, and the one that runs wins silently. Plan, then preflight, then apply. The plan says what would change; the preflight proves the world is ready — account, zone, image, bucket, two distinct keys — BEFORE anything is built, which is where a rebuild used to find out. A preflight that fails creates nothing. The compiled cluster document is WRITTEN DOWN before anything is built, and the path is printed. If the install half fails, the cluster exists and kubox admin install -f <that file> finishes the job — you do not start over. --plan renders the transaction it would perform and performs none of it. That is the same object this command checks and prints before acting, not a summary of one.

Options

Global options

See global options.

SEE ALSO

  • kubox plane - Describe and build a management plane from one document