Deprecated state of a Cluster Plan

< publish | cluster plans states

This section takes a closer look at the deprecated state of a cluster plan. When a cluster plan is no longer suitable for provisioning new clusters - such as when a Kubernetes version becomes outdated - it can be marked as deprecated. This prevents further use for new cluster creation, but allows existing clusters to continue functioning without disruption. Deprecated plans remain visible for auditing or reference purposes, ensuring platform engineers can manage legacy configurations.

CLI Instructions

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

• appvia.io/publishState: Deprecated means that the plan is no longer in use.
• appvia.io/published: false confirms the plan is no longer available for provisioning in scoped workspaces or stages.

Here's a YAML snippet illustrating the deprecated state:

apiVersion: compute.appvia.io/v2beta2
kind: ClusterPlan
metadata:
  annotations:
    appvia.io/publishState: Deprecated
    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 the deprecated state have a deprecated in the State column

To deprecate a cluster plan:

• Click the kebab menu
• Click the Deprecate option (only available for plans that aren't already deprecated)

What comes next?

• Consume a cluster plan

Related Reading

• Create a cluster plan
• View existing cluster plans
• Scope Scenarios