Skip to main content

Overview of Versioned Cluster Plans

introduction to cluster plans

Prerequisite(s)


What are cluster plans?

A cluster plan is a versioned blueprint for provisioning one or more clusters. It details specific aspects of the cluster's provisioning configuration, including which cluster network specifications to use and which Wayfinder versioned packages to include for bootstrapping the cluster with software and services like ExternalDNS.


How do cluster plans fit in with the rest of Wayfinder?

Cluster plans are part of Wayfinder's broader process flow for creating Wayfinder-managed Kubernetes clusters as part of the developer self-service process. Below is a brief overview of the different process flow parts in Wayfinder that are used to create the cluster provisioning specification.

WWayfinder concepts for creating a cluster provisioning specification


Self-Service Cluster Creation Process

Administrators, workspace owners, or members initiate the self-service cluster creation process by specifying the cluster's provisioning specifications. These specifications can be used to provision the cluster directly via Wayfinder's CLI or User Interface, or indirectly through your CI pipeline.


Creating a Self-Service Cluster Provisioning Specification

Creating a cluster provisioning specification involves:

  • Specifying a Cloud Access: This specification enables Wayfinder to access the cloud provider with the necessary permissions to manage and provision clusters.
  • Specifying a Cluster Plan: A cluster plan includes:
    • Cluster Network Plan: Outlines the network specification for cluster provisioning.
    • Wayfinder Packages (Optional): Outlines the specification for each software/service that you want to use for bootstrapping the cluster during provisioning.
  • Compute Templates (Optional): Pre-defined specifications for various compute instance (node pool) configurations, such as high-performance or low-cost options, to accelerate cluster creation in workspaces.
  • Provisioning Policies: Enforces limits on self-service clusters such as cost restrictions, regions or permitted instance types.

This section focuses on cluster plans and their lifecycle.


What comes next?