Skip to main content

Draft state of a Cluster Plan

< promote overview | cluster plans states

This section takes a closer look at the draft state of a cluster plan. When you create a new cluster plan, it starts in a draft state. This ensures that it is not immediately available in the scoped workspaces or stages, giving platform engineers time to review, make changes, and validate the plan. The draft status applies to both new plans and new versions of existing plans.

If a previously published plan is set back to draft status, it will become unavailable for self-service cluster provisioning until it is revalidated and republished.


CLI Instructions​

The publishState and published annotations show the state of a cluster plan.

  • appvia.io/publishState: Draft means the plan allows further edits. Ensure that you don't upate the metadata name, otherwise you'll create a new plan.
  • appvia.io/published: false confirms the plan is not yet available for provisioning in scoped workspaces or stages.

Here's a YAML snippet illustrating the draft state:

apiVersion: compute.appvia.io/v2beta2
kind: ClusterPlan
metadata:
  annotations:
    appvia.io/publishState: Draft
    appvia.io/published: 'false'

Web Interface Instructions​

  • Expand Admin, and then navigate to Kubernetes > Cluster Plans
  • Click on the name of a cluster plan
  • Plans in draft state have a draft value in the State column

To put a cluster plan back in draft:

  • Click the kebab menu
  • Click the Return to draft option (only available for plans that aren't already in draft)
Cluster Plan Promote - Draft Status


What comes next?​


Last updated