Prerequisites
- A verified account with a payment method.
- A project selected in the dashboard.
kubectlinstalled on your machine.
Create a Cluster
1
Open Cluster creation
Go to LKS in the sidebar and click Create Cluster.
2
Select a location
Choose the region where the Cluster runs. Plan availability and pricing vary by region.
3
Name the Cluster
Enter a name of 3-63 lowercase letters, numbers, or hyphens, starting and ending with a letter or number. It must be unique within the project.
4
Describe the Cluster (optional)
Add an optional description, up to 200 characters, to record what the Cluster is for.
5
Choose a Kubernetes version
Select the Kubernetes version for the Control Plane. The newest available version is selected by default.
6
Add Node Pools
Add one or more Node Pools. Each Node Pool has a Plan and a number of Nodes, and can carry its own Labels and Taints. See Node Pools for details.
7
Configure networking (optional)
Expand Cluster networking to set custom Pod, Service, and Node CIDRs. Most Clusters use the defaults. See Cluster networking.
8
Create
Review the hourly price and click Create Cluster. You’re taken to the Cluster overview while it provisions.
The Control Plane is fully managed. You don’t size or access Control Plane Nodes, and no SSH keys are needed to create a Cluster.
Cluster networking
A Cluster has three IP ranges: the Pod CIDRs, the Service CIDRs, and the Node CIDRs. LKS applies defaults that fit most Clusters, so you can accept them and skip this. To set your own ranges, expand Cluster networking in the create form and enter one IPv4 CIDR per field.Each field is a list (
pod_cidrs, service_cidrs, node_cidrs) in the create cluster API, but only a single value per field is supported today.Only IPv4 ranges are accepted, and each must be a network address (host bits set to 0), for example 10.0.0.0/12.How Pod addresses are allocated
Cilium runs the Cluster network with cluster-pool IPAM. It carves the Pod CIDRs into a/23 block for each Node, giving every Node about 510 Pod addresses, enough for the maximum of 500 Pods per Node. This per-Node block is fixed when the Cluster is created and is the same across every Node Pool.
Because Cilium manages Pod IPAM, LKS does not use the Kubernetes Node.spec.podCIDRs field. Ignore it: it isn’t populated and isn’t the source of truth for a Node’s Pod range. That range is recorded on the Node’s CiliumNode resource instead.
Sizing custom ranges
Each Node takes a/23 from the Pod CIDRs, so a shorter prefix allows more Nodes:
Size the Node CIDRs to hold at least as many addresses as the Pod CIDRs allow Nodes. A simple rule is to set the Node CIDR prefix to the Pod CIDR prefix plus 9: the default
/12 supports about 2,048 Nodes, matched by the default /21 Node CIDRs.
Cluster status
The Cluster list and overview show the current state:Access the Cluster
Download the kubeconfig from the Cluster Overview tab, under Cluster access:- Download kubeconfig: save the file to your machine.
- Copy to clipboard: copy the kubeconfig contents.
- View: preview the kubeconfig in the dashboard.
kubectl:
Name and description
On the Settings tab you can edit the Cluster’s Name (its display name) and its Description (up to 200 characters).Upgrade the Kubernetes version
Latitude.sh publishes the Kubernetes versions available for upgrade. To upgrade the Control Plane, open the Settings tab. When a newer version is available, the Version row shows Upgrade to{version}; otherwise it shows Up to date.
Node Pools stay on their current version until you upgrade them, and a Node Pool can run at most one minor version behind the Control Plane. Upgrade each pool after the Control Plane. See Upgrade a Node Pool.