Deploy a Kubernetes Cluster

Create a Managed Kubernetes Cluster from the Deploy Kubernetes page in my.cubepath.com. CubePath runs the control plane for you while your worker nodes run on CubePath VPS that you size and scale — you just download a kubeconfig and use kubectl like any other cluster. Most options are pre-filled, so you can launch in a few clicks.

Note: Your account must be verified before you can deploy.

Deploy

### Name your cluster
Pick the **project** and a **cluster name** (lowercase letters, numbers and dashes).

### Choose version and control plane
Select the **Kubernetes version** (the default is pre-selected) and optionally enable a **high-availability control plane** (+$20.00/mo).

### Pick region and instance type
Choose a **location** in **Miami (MIA)**, **Houston (HOU)** or **Barcelona (BCN)**, then an instance type for the worker nodes.

### Configure node pools
Set each pool's **name**, **plan** and **node count** (1–100). **Auto Scale** is on by default; add more pools with **Add Pool**.

### Deploy
Optionally adjust **Advanced Settings** (IPv4/IPv6, pod/service CIDRs, private network), then click **Deploy Cluster**.

Important: Disabling public IPv6 requires attaching a private network first, so worker nodes stay reachable.

Access

Clusters are accessed with kubectl, not SSH. Once the cluster is active, open it, click Cluster Management, then Download Kubeconfig to get the <cluster>-kubeconfig.yaml file. Point kubectl at it:

export KUBECONFIG=./<cluster>-kubeconfig.yaml
kubectl get nodes

Expose your apps

A fresh cluster has no public entry point. To send internet traffic to your services, install an ingress controller from the Addons tab, then put a Load Balancer in front of the worker nodes (deploy one from the Load Balancers tab). For internal-only clusters, attach a private network at deploy time and skip public worker IPs.

Good to know

  • Networking — pods and services use their own ranges (defaults 10.42.0.0/16 and 10.43.0.0/16); custom CIDRs must not overlap each other or your private network.
  • Managed control plane — CubePath runs and maintains it, and there's no SSH to it. You interact with the cluster only through the Kubernetes API (the kubeconfig).
  • One location per cluster — the workers and the private network live in a single region.
  • Limits — 1–10 node pools per cluster, 1–100 nodes per pool, and up to 50 labels and 50 taints per pool.
  • API — everything here is also available over the CubePath API (Authorization: Bearer <token>, scopes kubernetes:read / kubernetes:write). See api.cubepath.com.