Opencenter_Cluster_Deploy :: openCenter Community Documentation

opencenter cluster deploy

Deploy a cluster from its openCenter configuration

Synopsis

Deploy a cluster from its openCenter configuration.

This command provisions infrastructure and deploys Kubernetes based on the cluster configuration. The process is resumable; if a step fails, fix the issue and re-run deploy to continue from the saved state.

When used with the global --dry-run flag, deploy prints a provider-specific plan only. No commands are run, no files are written, locks are not acquired, and local or remote prerequisites are not fully validated.

opencenter cluster deploy [name] [flags]

Options

      --break-lock                 force removal of an existing operation lock before deploying
      --container-runtime string   container runtime for kind clusters (docker or podman)
      --debug                      print deploy step debug details before each step runs
      --from-step string           restart deploy from the specified step ID
  -h, --help                       help for deploy
      --kubeconfig string          path to kubeconfig used by deploy actions (defaults to the cluster-owned kubeconfig path)
      --log string                 log file path (defaults to <state_dir>/logs/bootstrap/<org>/<name>/bootstrap-YYYYMMDDTHHMMSSZ.log)
      --restart                    rerun all deploy steps and ignore saved state
      --step string                run a single deploy step by ID

Dry Run

opencenter cluster deploy <name> --dry-run prints the resolved cluster paths, runtime artifact paths, and provider-specific steps that would run during a real deploy. This is a planning aid, not a full simulation of Kind, Flux, Git, OpenTofu, Kubernetes, or cloud-provider behavior.

Debug

opencenter cluster deploy <name> --debug prints a debug block before each deploy step runs. The block includes the step name, environment metadata, working directory, and command plan for that step.