Skip to main content
Kubernetes clusters are the foundation of your container infrastructure. Configure cluster settings, provision nodes, and manage the complete cluster lifecycle.

​
Key Concepts

Cluster

A Kubernetes cluster with control plane and worker nodes.

Build

Automated provisioning that installs Kubernetes components on nodes.

Reset

Complete cluster teardown that removes all configurations.

Upgrade

Rolling update of Kubernetes and component versions.

​
Required Permissions

​
How to Create a Cluster

1

Click Add Cluster

Click the Add Cluster button.
2

Configure Basic Settings

  • Cluster Name - Unique identifier
  • Cluster Domain - DNS domain (e.g., cluster.local)
3

Configure Versions

  • K8s Version - Select Kubernetes version
  • Runtime - Container runtime (containerd)
  • Runtime Version - Specific runtime version
4

Configure Networking

  • Pod Network - CIDR for pod IPs (e.g., 10.244.0.0/16)
  • Service Network - CIDR for services (e.g., 10.96.0.0/12)
  • CNI Plugin - Network plugin (Calico, Cilium, etc.)
5

Configure Options

  • Proxy Mode - iptables (default) or ipvs
  • CGroup Driver - systemd (recommended) or cgroupfs
  • Metrics Server - Enable for resource monitoring
6

Create

Click Create Cluster to save the configuration.
Creating a cluster only saves the configuration. Run the Build operation to provision Kubernetes on the nodes.

​
How to Build a Cluster

Building installs Kubernetes components on all configured nodes.
1

Open Cluster

Click on the cluster to open details.
2

Click Build

Click Build in the Operations section.
3

Review Node Readiness

The wizard checks all nodes for:
  • SSH connectivity
  • OS compatibility
  • Disk, memory, and CPU availability
  • Required ports
4

Review Configuration

Verify Kubernetes version, runtime, CNI plugin, and node distribution.
5

Start Build

Click Start Build to begin provisioning.
Build will fail if any node has critical issues. Resolve blockers before attempting to build.

​
How to Reset a Cluster

Resetting removes all Kubernetes configurations and returns nodes to clean state.
1

Open Cluster

Click on the cluster to open details.
2

Click Reset

Click Reset in the Operations section.
3

Review Impact

The wizard shows affected resources:
  • Running workloads (pods, deployments)
  • Storage (PVs, PVCs)
  • Network resources (services, ingresses)
  • Configuration (configmaps, secrets)
4

Complete Safety Checklist

Acknowledge that:
  • Data has been backed up
  • Workloads will be terminated
  • Storage data will be lost
  • Action is irreversible
5

Confirm Reset

Type the cluster name to confirm.
Reset is irreversible. All workloads, configurations, and persistent data will be permanently deleted.

​
How to Upgrade a Cluster

1

Open Cluster

Click on the cluster to open details.
2

Click Upgrade

Click Upgrade in the Operations section.
3

Select Target Versions

Choose target versions for Kubernetes and components.
4

Execute Upgrade

The upgrade performs a rolling update to minimize downtime.
Upgrade is only available for clusters in Ready state.

​
How to Delete a Cluster

1

Find the Cluster

Locate the cluster in the list.
2

Click Delete

Click the delete icon.
3

Confirm

Confirm the deletion.
Deleting a cluster configuration does not reset the nodes. Run Reset first to clean up nodes before deleting.

​
Troubleshooting

  • Check SSH connectivity to all nodes
  • Verify nodes meet minimum resource requirements
  • Ensure required ports are not in use
  • Check OS compatibility
  • Check operation logs for errors
  • Verify network connectivity between nodes
  • Ensure CNI plugin installed correctly
  • Check control plane component logs
  • Verify API server is running
  • Check network connectivity to master nodes
  • Ensure kubeconfig is correct
  • Verify certificates are valid
  • Check operation logs for specific errors
  • Verify SSH connectivity to all nodes
  • Some resources may have finalizers preventing deletion

​
FAQ

Creating saves the cluster configuration. Building actually provisions Kubernetes on the nodes. You must create first, then build.
Use the Upgrade operation to change versions. Major version changes may require reset and rebuild.
All data is permanently deleted including PersistentVolumes, ConfigMaps, Secrets, and container data.
iptables is the default and works for most clusters. ipvs provides better performance for large clusters with 1000+ services.
Required for MetalLB Layer 2 mode. Prevents nodes from responding to ARP requests for IPs they don’t own.