What are Templates

Templates define a baseline configuration applied to every tenant cluster or space created from them. They are how Platform administrators enforce consistency across a fleet without requiring each user to configure resources manually.

Templates solve a governance problem at scale. Instead of trusting users to apply the right security settings, resource limits, and networking policies, you encode those requirements into a template and make it the only option available in a project.

What templates can include

• A base vcluster.yaml configuration defining the tenant cluster's control plane, worker node type, backing store, and sync settings
• Resource quotas, limit ranges, and network policies for namespace-level isolation
• Kubernetes objects deployed into the tenant cluster at creation time, such as tooling, pre-populated test data, or CRDs
• Apps — packaged applications deployed into the tenant cluster when it is created
• Parameters that let users customize within defined bounds at creation time

How templates work with projects

Templates are created at the global level by Platform administrators. To make a template available to project members, it must be explicitly allowed within that project. Admins can set a default template for a project, restrict members to a specific set, or allow all templates.

This two-level model (global definition, per-project access) means you can maintain a library of approved configurations and expose only the relevant ones to each team or customer.

Create a template →

Allow templates in a project →