Control Self-Service Cluster Provisioning with Provisioning Policies

In previous posts, we’ve covered how Wayfinder’s self-service feature makes it easy for developers to provision Kubernetes clusters. But how can you ensure this self-service capability remains cost-effective and compliant? In this blog, we’ll explore Wayfinder’s provisioning policies and how they provide essential guardrails. With built-in boundaries for cost and resources, these policies enable flexibility without compromising on compliance.

‍What are Provisioning Policies?

Provisioning policies in Wayfinder allow you to set boundaries for cloud cluster creation, whether on AWS, Azure, or GCP. These policies enable platform engineers to define where clusters can be deployed, select instance types, and enforce cost thresholds within a self-service framework.

‍

Setting up these boundaries ensures that cloud resources remain within budget and meet organisational standards, so developers can provision clusters without delays, and platform engineers can have peace of mind.

‍

Here’s a quick look at key provisioning policy settings for AWS, Azure, and GCP:

‍

• Region: Specify approved deployment regions for cost management and data sovereignty.
• Max Clusters: Set limits on the number of clusters a workspace can create (e.g., dev workspaces in a non-prod stage).
• Instance Types: Limit available instance types, ensuring resources fit workload requirements.
• Cost Limits: Define maximum cost per cluster to manage budget effectively.

‍

How Wayfinder’s Provisioning Policies Help

Provisioning policies simplify infrastructure management, letting you set clear, cost-effective parameters for cloud resource usage. Here’s how they can benefit your team:

‍

Use Case 1

Empower developers to provision clusters without the hassle of approval tickets. Wayfinder’s provisioning policies allow you to set up guardrails in advance, so developers can select cluster settings while Wayfinder manages the rest.

‍

• Speed: Provision clusters quickly without approval bottlenecks.
• Simplicity: Establish boundaries once and apply them across teams.
• Cost Awareness: Keep budgets in check with clear expectations.

‍

Use Case 2

Provisioning policies also give developers the flexibility to select instance types, regions, and costs within predefined limits. This allows them to adjust clusters as needed for their applications, all while staying within guardrails.

‍

• Flexibility: Configure clusters to meet application needs without exceeding limits.
• Protection: Enforce cost-efficiency and compliance for every cluster.
• Autonomy: Work at your own pace, free from manual checks or delays.

‍

What Does It Look Like?

Platform Engineers

• Create a provisioning policy, scoping it to the appropriate stage (prod/non-prod) and workspaces.
• Define restrictions such as allowed regions, maximum cluster and node count, and instance types.
• Apply the policy through Wayfinder’s Web Interface, CLI, or CI/CD pipeline.

‍

‍

‍

Developers

When provisioning a cluster, developers see only the resources available to them according to the provisioning policy:

‍

• Greyed-Out Options: Signal restrictions for regions or instance types.
• Budget Alerts: Warn if the configuration risks exceeding cost limits.
• Customisation: Configure resources within set boundaries for workload needs.

‍

‍

Conclusion

Appvia Wayfinder provisioning policies streamline cloud resource management, enabling fast, cost-effective, self-service cluster provisioning while ensuring compliance across multiple clouds. Set boundaries that empower your team to move quickly, efficiently, and within budget.