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.

What "managed" means here

CubePath runs the API server, scheduler, controller manager and etcd, keeps them patched and healthy, and hands you an endpoint. You run everything above that line: your workloads, your node pools, your add-ons.

Each worker is a real VPS in your account, billed like any other VPS. That's the cost model — you pay for the workers you run, plus the HA control plane if you enable it.

Deploy

  1. 1
    Name your cluster
    Pick the project and a cluster name (lowercase letters, numbers and dashes).
  2. 2
    Choose version and control plane
    Select the Kubernetes version (the default is pre-selected) and optionally enable a high-availability control plane — 2 control-plane replicas, +$20.00/mo. Worth it for production; leave it off for dev and test.
  3. 3
    Pick region and instance type
    Choose a location in Miami (MIA), Houston (HOU) or Barcelona (BCN), then an instance type for the worker nodes.
  4. 4
    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.
  5. 5
    Deploy
    Optionally adjust Advanced Settings (IPv4/IPv6, pod/service CIDRs, private network), then click Deploy Cluster.

The cluster provisions in the background; its status moves through Provisioning to Active.

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

From there it's a standard cluster: apply manifests, install Helm charts, run whatever you like.

Expose your apps

A fresh cluster has no public entry point. To send internet traffic to your services:

  1. 1
    Install an ingress controller
    Pick one from the Addons tab.
  2. 2
    Put a load balancer in front
    Deploy one from the Load Balancers tab, targeting the worker nodes.
  3. 3
    Point DNS at it
    Create a record in DNS records for the load balancer's IP.

For internal-only clusters, attach a private network at deploy time and skip public worker IPs.

Protection and deletion

Enable Protection blocks accidental deletion of the cluster. Deleting is permanent: it removes the cluster, every node pool, and destroys all worker VPS instances. Disable protection first if it's on.

Limits and constraints

ThingLimit
Node pools per cluster1–10
Nodes per pool1–100
Labels per pool50
Taints per pool50
  • Pod and service CIDRs default to 10.42.0.0/16 and 10.43.0.0/16. Custom ranges must not overlap each other, the node network, or your private network.
  • No SSH to the control plane. You interact with the cluster only through the Kubernetes API.
  • One location per cluster. Workers and the private network live in a single region.

The cluster tabs

Node Pools, Network, Addons, Load Balancers, Metrics and Activity.