Skip to main content

Overview

Cluster templates are reusable blueprints that define the configuration for Kubernetes clusters. A template captures the Kubernetes version, node image, instance flavor, network driver, and storage backend. Once created, a template can be used to deploy multiple clusters with consistent configurations. Your administrator can publish public templates shared across all projects; you can also create private templates for your own use.
Prerequisites
  • An active Xloud account with project access
  • A keypair created in your project for node SSH access
  • Compute quota sufficient for cluster nodes
  • A project network with external access

Template Fields Reference

FieldRequiredDescriptionRecommended Value
NameYesUnique template identifierk8s-1.29-prod
Container Infra DriverYesCluster provisioning enginekubernetes
ImageYesBoot image for cluster nodesfedora-coreos-39
KeypairYesSSH key for node accessYour project keypair
FlavorYesInstance size for worker nodesm1.large (4 vCPU / 8 GB)
Master FlavorYesInstance size for master nodesm1.xlarge (8 vCPU / 16 GB)
Network DriverYesContainer network interfacecalico (production)
Volume DriverYesPersistent volume backendcinder
External NetworkYesFloating IP sourcepublic
DNS NameserverYesResolver for cluster nodes8.8.8.8
Master LB EnabledNoLoad balance master nodesTrue (HA)
Docker Volume SizeNoContainer storage per node (GB)50
Floating IP EnabledNoAssign floating IPs to nodesTrue

Create a Cluster Template

Navigate to Cluster Templates

Log in to the Xloud Dashboard (https://connect.<your-domain>) and navigate to Project → Containers → Cluster Templates.

Create the template

Click Create Cluster Template and fill in the required fields using the reference table above.
For production clusters, enable Master LB to place a load balancer in front of master nodes and set Master Count to 3 when deploying the cluster.

Configure advanced options

Expand Advanced to set optional parameters:
  • Insecure Registry: Internal container registry URL (if used)
  • Fixed Network / Subnet: Pin cluster nodes to a specific project network
  • Labels: Key-value labels for platform-specific options (e.g., auto_healing_enabled=true)

Save the template

Click Create Cluster Template. The template appears in the list with status ACTIVE.
Template created with status ACTIVE and visible in the template list.

Network Driver Comparison

The network driver (CNI plugin) is configured at template creation and cannot be changed after cluster deployment.
DriverNetwork PolicyPerformanceRecommended For
calicoFull NetworkPolicy enforcementModerateProduction workloads requiring pod isolation
flannelNoneHigher (simpler overlay)Development and test clusters
Use calico for all production templates. Flannel is appropriate only for isolated test environments where Kubernetes NetworkPolicy is not required.

Manage Existing Templates

Navigate to Project → Containers → Cluster Templates. From this view you can:
  • Click a template name to view its full configuration
  • Click Actions → Delete to remove unused templates (templates in use by clusters cannot be deleted)

Next Steps

Deploy a Cluster

Provision a Kubernetes cluster from your template in minutes.

Node Groups

Add specialized node pools with different flavors to your cluster.

Access Cluster

Download kubeconfig and connect kubectl to your cluster.

Kubernetes Admin Guide

Administrator reference for managing public templates and quotas.