airshipctl/airshipctl_cluster_init.md at 622d45f3bddc98e96abac49497909444ae666ea4

Michael Beaver 193dc935f1 Refactor subPath out of config manifests

This change removes the SubPath entry portion of the config manifests, and
refactors several areas that used it. This also updates unit tests to
reflect the new changes.

Closes: #255

Change-Id: Ibbb519a3f1fb28a1594e971274c5de54b99c867e

2020-11-04 09:30:03 -06:00

1.7 KiB

Raw Blame History

airshipctl cluster init

Deploy cluster-api provider components

Synopsis

Initialize cluster-api providers based on airshipctl document set. document set must contain document of Kind: Clusterctl in phase initinfra. Path to initinfra phase is defined in the initinfra phase document located in the manifest repository. Clusterctl document example:

apiVersion: airshipit.org/v1alpha1 kind: Clusterctl metadata: labels: airshipit.org/deploy-k8s: "false" name: clusterctl-v1 init-options: core-provider: "cluster-api:v0.3.3" bootstrap-providers: - "kubeadm:v0.3.3" infrastructure-providers: - "metal3:v0.3.1" control-plane-providers: - "kubeadm:v0.3.3" providers:

name: "metal3" type: "InfrastructureProvider" versions: v0.3.1: manifests/function/capm3/v0.3.1
name: "kubeadm" type: "BootstrapProvider" versions: v0.3.3: manifests/function/cabpk/v0.3.3
name: "cluster-api" type: "CoreProvider" versions: v0.3.3: manifests/function/capi/v0.3.3
name: "kubeadm" type: "ControlPlaneProvider" versions: v0.3.3: manifests/function/cacpk/v0.3.3

airshipctl cluster init [flags]

Examples


# Initialize clusterctl providers and components
airshipctl cluster init

Options

  -h, --help                help for init
      --kubeconfig string   Path to kubeconfig associated with cluster being managed

Options inherited from parent commands

      --airshipconf string   Path to file for airshipctl configuration. (default "$HOME/.airship/config")
      --debug                enable verbose output

1.7 KiB Raw Blame History