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
| Type | Visibility | Created By | Used By |
|---|---|---|---|
| Public | All projects | Administrator | Any project team |
| Private | Current project only | Any user | Own project only |
Create a Public Template
- Dashboard
- CLI
Navigate to Cluster Templates (admin)
Log in to the Xloud Dashboard (
https://connect.<your-domain>) and navigate to
Admin → Containers → Cluster Templates.Create template
Click Create Cluster Template and fill in the fields. Set Public to
True.| Field | Recommended Value | Notes |
|---|---|---|
| Master Flavor | m1.xlarge | Control plane: 8 vCPU / 16 GB minimum |
| Master LB Enabled | True | Required for HA control plane |
| Network Driver | calico | NetworkPolicy enforcement for production |
| Volume Driver | cinder | Enables PersistentVolumeClaims |
| Docker Volume Size | 50 GB | Container image storage per node |
| Floating IP Enabled | True | kubectl access via floating IP |
| Public | True | Share across all projects |
Add auto-healing labels
In the Labels field, add:This enables automatic node replacement when a node becomes unhealthy.
Template Version Lifecycle
Maintain a clear versioning strategy for public templates as Kubernetes versions are released and deprecated.| Stage | Action |
|---|---|
| New version available | Create new public template (e.g., k8s-1.30-standard) |
| Previous version stable | Keep both templates public — users can choose |
| Previous version deprecated | Mark old template as non-public; notify project teams |
| Previous version retired | Delete old template after all clusters have been upgraded |
Make an existing template private (deprecation)
Delete a retired template
Recommended Label Configuration
Labels control advanced Kubernetes and platform features at the template level.| Label | Value | Effect |
|---|---|---|
auto_healing_enabled | true | Automatically replace unhealthy nodes |
auto_scaling_enabled | true | Enable Cluster Autoscaler |
container_runtime | containerd | Set container runtime (required for Kubernetes 1.24+) |
cloud_provider_enabled | true | Enable Xloud cloud provider for LoadBalancer services |
cinder_csi_enabled | true | Enable Cinder CSI driver for PersistentVolumeClaims |
Validation
- Dashboard
- CLI
Navigate to a non-admin project and check Project → Containers → 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.