Skip to main content

Validate a Cluster Plan

< introduction | validate cluster plans

This section covers the "Validate" phase of the cluster plan's lifecycle.

Cluster Plan Lifecycle - Validate


Prerequisite(s)​


Overview​

Use Wayfinder's CLI to validate a cluster plan before making it available to workspace users.

The wf validate clusterplan allows you to create a cluster to test a plan or record a validation of a plan given an existing cluster. When validating a plan with a new cluster, you can choose to delete or keep the cluster after validation, depending on the result.


CLI Instructions​

Use the wf validate clusterplan --plan PLAN --plan-version SEMVER [flags] command to validate a cluster plan.

You have several validation options:

  • Use the dry-run flag to simulate validation without provisioning any clusters.
  • Use the --cluster CLUSTER flag to validate the plan of an existing cluster.
  • Omit the --cluster flag to provision a cluster for validation. In this case, you can:
    • Automatically delete the cluster after validation, regardless of the outcome, using the --delete-on-completion flag.
    • Delete the cluster only if validation succeeds (keep on failure) with the --delete-on-success flag.
    • Retain the cluster after validation using the --keep-cluster flag.


Validate a Cluster Plan


wf -w sand2 validate clusterplan --plan aks-general-purpose --plan-version 1.0.1 --stage nonprod --cloud-access joebloggs-sand2 --region uksouth --compute-template aks-general-purpose --keep-cluster

◉ Creating cluster plan validation
✔ Cluster plan validation created - aks-general-purpose-1.0.1-t8r64
◉ Validating cluster plan (validation "aks-general-purpose-1.0.1-t8r64")
  ◉ Waiting for (1h0m0s) for cluster plan validation "aks-general-purpose-1.0.1-t8r64" to be ready
  ◉ Checking all required cluster plans exists.
  ✔ Cluster plan object exists

  ◉ Waiting for wayfinder cluster object to be created
  ✔ Cluster object has been created

  ◉ Waiting for cluster to be built in cloud
    ✔ Cluster created aks-gexcnfn
    ◉ Waiting for Cluster plan valid.
    ✔ Cluster plan valid complete
    ◉ Waiting for Cloud account available
    ✔ Cloud account available complete
    ◉ Waiting for Network provisioned.........
    ✔ Network provisioned complete
    ◉ Waiting for Cluster provisioned.............................................................
    ✔ Cluster provisioned complete
    ◉ Waiting for Service account ready...............
    ✔ Service account ready complete
    ◉ Waiting for Node pools provisioned.....
    ✔ Node pools provisioned complete
    ◉ Waiting for Cluster configured
    ✔ Cluster configured complete


  ✔ Cluster has been built

  ◉ Waiting for packages to be ready
    ◉ ingress-nginx (4.10.1-1) Waiting for package release
    ◉ cert-manager (1.14.5-1) Waiting for package release
    ◉ external-dns (7.2.1-3) Waiting for package release
    ◉ kyverno (2.7.3-5) Waiting for package release
    ◉ terranetes-controller (0.7.12-1) Waiting for package release
    ✔ terranetes-controller (0.7.12-1) Namespace "terraform-system" exists
    ✔ terranetes-controller (0.7.12-1) Workload identity (cloud access) has valid template
    ✔ cert-manager (1.14.5-1) Namespace "cert-manager" exists
    ✔ cert-manager (1.14.5-1) Workload identity (cloud access) has valid template
    ✔ terranetes-controller (0.7.12-1) Workload identity (cloud access) is provisioned
    ✔ terranetes-controller (0.7.12-1) Helm repository verified
    ✔ terranetes-controller (0.7.12-1) Helm values ready
    ✔ external-dns (7.2.1-3) Namespace "external-dns" exists
    ✔ external-dns (7.2.1-3) Workload identity (cloud access) has valid template
    ✔ terranetes-controller (0.7.12-1) Helm release created/updated
    ✔ terranetes-controller (0.7.12-1) Helm release successful
    ◉ Waiting on overall readiness.............................
  ✔ Packages are ready


  ✔ Cluster plan validation is complete

✔ Cluster plan validation succeeded


What comes next?​


Last updated