cub cluster app-bootstrap

Create a cluster's apps Space and bootstrap its root in the controller

Synopsis

The third part of "cub cluster attach", on its own, for a cluster "cub cluster svc-account-bootstrap" set up. It finishes the attachment without argobot, as "cub cluster attach --no-k8sbot" does; "cub cluster k8sbot-install" adds argobot afterwards.

In ConfigHub it creates the apps Space, -argo-apps (-sveltos-apps or -flux-apps with Sveltos or Flux), releasing to the cluster's OCI target, and in it the root Unit: an Argo CD Application, a Sveltos ClusterProfile, or a Flux OCIRepository and Kustomization, that pulls the apps Space's own Release from ConfigHub's OCI registry with the pull token "svc-account-bootstrap" put in the cluster. Its first Release is published.

In the cluster the root is applied once with kubectl; from then on the controller pulls everything else from ConfigHub, so each Unit "cub variant create --target" adds to the apps Space becomes a deployment the controller runs. Without argobot, a Sveltos or Flux root polls its Release every minute.

--prune lets the controller delete what a removed deployment deployed; see "cub cluster attach --help".

Examples: cub cluster create lab cub cluster controller-install lab --provider kind cub cluster svc-account-bootstrap lab cub cluster app-bootstrap lab cub cluster k8sbot-install lab

cub cluster app-bootstrap <name> [flags]

Options

  -h, --help    help for app-bootstrap
      --prune   let the controller delete what a removed deployment deployed: the root prunes deployments whose Units leave the apps space (Sveltos's always does), and deployments created later prune what they deployed

Options inherited from parent commands

      --context string   The context to use for this command
      --debug            Debug output

cub cluster app-bootstrap