Skip to main content

Scenario 5: Inactive and not visible in any Workspaces

< scenario four | cluster plan scope examples

When to use?​

Use this scenario when you want to create a cluster plan that is neither visible nor usable to users in workspaces.

Note that the cluster plan needs to be in a 'published' state, before workspace users can provision clusters using that plan. See the promote section for more details.


Configuration Overview​


Cluster Plan Scoped Scenario 5


Initial configuration when first created​

  • Stage: Inactive (toggle on, but don't select any stages)
  • Workspace: Inactive (toggle on, but don't select any workspaces)
  • Cloud Access: None
  • Visibility: The cluster plan is neither visible nor usable. No clusters can be created using this plan.

Updated configuration​

N/A


Outline of steps​

  1. Initial Setup: Create the initial version of your cluster plan with the stage and workspace toggles on, but without selecting any stages or workspaces. The scope will be displayed as inactive.
  2. Work in Progress: Continue working on your plan, knowing that nobody can see it and no clusters can be created using this cluster plan.

CLI Instructions​

  1. Get the yaml for your existing cluster plan:

wf get clusterplan aks-hardened --version 1.0.0 -o yaml > MYPLAN.yaml

This copies the the aks-hardened cluster plan and places it in a file MYPLAN.yaml.


  1. Ensure that the YAML look as the snippet below:
  scope:
    allStages: false
    allWorkspaces: false
    allowedStages: []
  1. Follow one of the other scenarios once you're ready to extend the cluster plan scope to a wider audience.


Web Interface Instructions​

Steps

  • Expand Admin, and then navigate to Kubernetes > Cluster Plans
  • Click on the Name of your cluster plan.
  • Click on the Version of the cluster plan that you want to premote to a wider scope.
  • Click the Edit button.
  • Navigate to the Scope section:
    • Set the stages toggle to on, but do not select any of the stages.
    • Set the workspaces toggle to on, but do not select any of the workspaces.
  • Navigate to the Summary and ensure that the scope is as you intended.
  • Navigate to the YAML section and either Apply the YAML or use Wayfinder's CLI to apply it, or commit the YAML to your CI pipeline.

Screenshot(s)

UI Selections



Last updated