Overview
Administrators create and publish public cluster templates that are shared across all projects. Public templates provide standardized, pre-approved Kubernetes configurations — ensuring project teams use consistent Kubernetes versions, flavors, and network drivers without needing to configure templates themselves. This page covers creating, updating, and retiring public templates.Public vs Private Templates
Create a Public Template
- Dashboard
- CLI
Navigate to Cluster Templates (admin)
Navigate to
Container (admin view) > Cluster Templates.
Create template
Click Create Cluster Template and fill in the fields. Set Public to
True.Add auto-healing labels
In the Labels field, add:This enables automatic node replacement when a node becomes unhealthy.
Save
Click Create Cluster Template. The template appears in all project template
lists immediately.
Template is visible in all projects and usable for cluster creation.
Template Version Lifecycle
Maintain a clear versioning strategy for public templates as Kubernetes versions are released and deprecated.Make an existing template private (deprecation)
Delete a retired template
Recommended Label Configuration
Labels control advanced Kubernetes and platform features at the template level.Validation
- Dashboard
- CLI
Navigate to a non-admin project and check Container > Cluster Templates.
Verify the public template is visible and selectable for cluster creation.
Public template is visible in all projects and usable for cluster creation.
Next Steps
Quotas
Set per-project limits on cluster and node counts.
Container Runtime
Configure the recommended container runtime for new templates.
Network Drivers
Choose CNI plugins and configure NetworkPolicy defaults.
Certificates
Manage cluster certificate authorities and perform CA rotations.
