Skip to Content
Open Beta — managed Kubernetes, DNS & more are live.
🐳

Managed Kubernetes clusters

Updated 2026-11-20
On this page

Managed Kubernetes clusters

Patrii Cloud runs the Kubernetes control plane for you and provisions worker nodes on demand. Create a cluster, download its kubeconfig, and deploy your workloads with the standard Kubernetes tools you already use.

A managed cluster removes the toil of building and operating Kubernetes yourself. Patrii provisions the control-plane and worker instances, wires up networking and the cloud integrations, and gives you a cluster you drive with kubectl, Helm and your CI pipelines.

The control plane can run as a single node or in a highly-available configuration with several control-plane nodes so one failure does not take the cluster's API offline. Worker nodes run your pods and are grouped so you can scale their count as your workloads grow.

Screenshot — The Kubernetes cluster list showing clusters with their status and Kubernetes version
The Kubernetes cluster list showing clusters with their status and Kubernetes version

Key concepts

Cluster — A Kubernetes control plane plus its worker nodes, managed as one resource.

Control plane — The nodes that run the Kubernetes API, scheduler and controllers; run several for high availability.

Worker node — An instance that runs your pods; the cluster has one or more of them.

kubeconfig — The credentials-and-endpoint file kubectl uses to talk to your cluster's API.

Node count — How many worker nodes the cluster runs; you can change it later.

Before you start

  • Enough compute quota for the control-plane and worker sizes you choose.
  • kubectl installed on your machine (and Helm if you use it).
  • A project network the cluster's nodes can use.

Step by step

  1. Open the create wizard

    Go to Kubernetes and choose Create cluster.

    Screenshot — The Create cluster button on the Kubernetes page
    The Create cluster button on the Kubernetes page
  2. Name it and pick a version

    Give the cluster a name and select a Kubernetes version from the supported list.

    Screenshot — The cluster name and Kubernetes version selection
    The cluster name and Kubernetes version selection
  3. Choose the control plane
    • Select the size for the control-plane nodes.
    • Choose a single control-plane node, or several for high availability so the API survives a node failure.
    Screenshot — The control-plane sizing step
    The control-plane sizing step
  4. Choose the worker nodes
    • Select the worker node size.
    • Set how many worker nodes to start with; you can change this later.
    Screenshot — The worker size and node-count step
    The worker size and node-count step
  5. Create and wait for ready

    Review the summary and create. The cluster provisions its nodes and moves to a ready state; this takes a few minutes.

    Screenshot — A cluster transitioning to the ready state
    A cluster transitioning to the ready state
  6. Download the kubeconfig and connect

    Open the cluster and download its kubeconfig, then point kubectl at it and confirm the nodes are Ready.

    Screenshot — The cluster detail page with the Download kubeconfig action
    The cluster detail page with the Download kubeconfig action

Examples

Use the downloaded kubeconfig with kubectl
export KUBECONFIG=~/Downloads/kubeconfig-my-cluster
kubectl get nodes
kubectl get pods -A
Deploy a sample workload
kubectl create deployment web --image=nginx
kubectl scale deployment web --replicas=3
kubectl expose deployment web --port=80 --type=LoadBalancer
Install a chart with Helm
helm repo add bitnami https://charts.bitnami.com/bitnami
helm install my-release bitnami/nginx

Limits & specifications

What the console gives you per cluster:

CapabilityWhat it does
Create / deleteProvision or tear down a whole cluster.
Scale workersChange the worker node count as load changes.
kubeconfigDownload admin or user-scoped credentials for kubectl and CI.
VersionsPick from the supported Kubernetes versions at create time.
Metrics & nodesSee cluster metrics and the state of each node.
Access (RBAC)Grant users and groups scoped access to the cluster.

Best practices

  • Run a highly-available control plane for anything you cannot afford to have offline during a node failure.
  • Keep the admin kubeconfig secret; hand out user-scoped, RBAC-limited access for day-to-day work.
  • Pin your manifests to a Kubernetes version and test before upgrading.
  • Expose services through a load balancer or ingress rather than individual node IPs.
  • Right-size workers and adjust the node count from metrics instead of over-provisioning up front.

FAQ

kubectl cannot reach the cluster.
Confirm KUBECONFIG points at the file you downloaded for this cluster, that the cluster is in a ready state, and that your network allows access to the cluster's API endpoint.
How do I add more capacity?
Increase the worker node count from the cluster's settings; new workers join and become schedulable automatically.
Can I give a teammate limited access?
Yes. Use the cluster's access controls to grant a user or group RBAC-scoped access instead of sharing the admin kubeconfig.
How do I run a LoadBalancer service?
Create a Service of type LoadBalancer; the cloud integration provisions a load balancer and assigns it an address.

Learn more

Everything you can do here in the console is also available through the Patrii Cloud API for automation and scripting.

Was this article helpful?
Thank you for your feedback. Still stuck? Contact us