wf init cluster
wf init cluster
Initialise a cluster
wf init cluster [flags]
Examples
# Initialise a single nonprod cluster named dev and write it to a file:
$ wf -w my_workspace init cluster dev --plan plan_name --plan-version 1.0.0 \
--stage nonprod --cloud-access cloud_access_config_name \
--region cloud_region_name --compute-template compute_template_name --out cluster-dev.yaml
# Initialise a single nonprod cluster named dev using a compute template from a file:
$ wf -w my_workspace init cluster dev --plan plan_name --plan-version 1.0.0 \
--stage nonprod --cloud-access cloud_access_config_name \
--region cloud_region_name --compute-template-file ./path/to/compute_template.yaml
Options
-a, --cloud-access string Name of the cloud access config to use for this cluster
-c, --compute-template string The compute template to use for this cluster
-f, --compute-template-file string Use a file for the compute template
-d, --description string A short description for the cluster
-h, --help help for cluster
-O, --out string File to write the YAML of the package to (default: output to standard out)
-p, --plan string Cluster plan that this cluster will use
-v, --plan-version string Cluster plan version that this cluster will use
-r, --region string The region for this cluster
-s, --stage string The stage for this cluster
Options inherited from parent commands
--debug Debug / trace logging (default: false)
--force Force operation to happen (default: false)
--no-wait Do not wait for resources to provision
-o, --output string Output format of the resource (json,yaml,table) (default "table")
--profile string Use a profile other than your current - to change current: wf use profile NAME
--show-headers Display headers on table out (default true)
--verbose Verbose logging (default: false)
-w, --workspace string Workspace to use - to change default: wf use workspace NAME
SEE ALSO
- wf init - Use wf init to create skeleton YAML structures for Wayfinder resources