Published state of a Cluster Plan
< draft | cluster plans states
This section takes a closer look at the published state of a cluster plan. Once a plan has been validated and its scope properly configured, it can be promoted to a published state. In this state, the cluster plan becomes available to users for provisioning self-service clusters based on the configurations set by platform engineers. Publishing marks the transition from preparation to active use.
CLI Instructions
The publishState and published annotations show the state of a cluster plan.
- appvia.io/publishState:
Publishedmeans that the plan has been published. - appvia.io/published:
trueconfirms the plan is available for provisioning in scoped workspaces or stages.
Here's a YAML snippet illustrating the published state:
apiVersion: compute.appvia.io/v2beta2
kind: ClusterPlan
metadata:
annotations:
appvia.io/publishState: Published
appvia.io/published: 'true'
Web Interface Instructions
- Expand Admin, and then navigate to Kubernetes > Cluster Plans
- Click on the name of a cluster plan
- Plans in published state have a
Publishedvalue in the State column - Click on the name of the cluster plan
- Plans in published state have a
Publishedtag in the infoview section.
To publish a cluster plan
- Click the kebab menu
- Click the Publish option (only available for plans that aren't already published)
Screenshot(s)
- View Published State:
- Publish a cluster plan: