Skip to main content

Overview of Compute Templates

introduction to compute templates


What are compute templates?

Compute templates are optional, predefined configurations specifying the scale and type of compute instances (node pools) needed for creating clusters. They enable developers to quickly set up self-service clusters with an optimal starting configuration, which they can further customise as necessary.


How do compute templates fit in with the rest of Wayfinder?

Compute templates are part of Wayfinder's broader process for creating Wayfinder-managed Kubernetes clusters, designed to simplify the developer self-service process. Below is a brief overview of the steps involved in creating a cluster provisioning specification, which Wayfinder then uses to provision the cluster.

Wayfinder 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:
  • 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.

Configuring Additional Policies

Cluster Access Policies and Cluster Policies are key to managing security, compliance, and access control within Wayfinder-managed clusters. Although these policies are not part of the self-service provisioning process itself, they are fully visible and configurable by administrators, enabling tailored management of permissions and governance as part of your overall cluster management strategy.

  • Cluster Policies (Optional): Uses Kyverno to define and enforce security and compliance rules for cluster management and control.
  • Cluster Access Policies: Grants users the right to gain short-lived access to a cluster themselves, or to assign permanent access to an access token.

This section focuses on compute templates.


What comes next?