Skip to main content
Latitude Kubernetes Service (LKS) is managed Kubernetes on bare metal. Latitude.sh runs the Control Plane; you run your Workloads on Node Pools. You get a conformant, upstream Kubernetes Cluster and a kubeconfig, then manage your applications with standard Kubernetes tooling.
LKS is in preview. Features and defaults may change. During the preview, LKS is managed from the dashboard; API, CLI, and SDK support is coming.

​
What Latitude.sh manages

  • Control Plane. The API server and etcd run as a managed, highly available Control Plane. You don’t size, access, or patch it.
  • Networking. Cilium is the Cluster CNI, configured and maintained for you.
  • LoadBalancer IPs. A Service of type LoadBalancer is assigned a Latitude Elastic IP announced over BGP. See Exposing Workloads.
  • Node images. Node operating system images are provided by Latitude.sh and roll out through Node Pool upgrades.

​
What you manage

  • Workloads. Your applications, their manifests, and their lifecycle.
  • Node Pools. The plan, size, Labels, and Taints of each Node Pool. See Node Pools.
  • Ingress and gateways. LKS load balancing is L4. Bring your own Ingress or Gateway controller for HTTP routing.
  • Observability, backups, and upgrades. You run your monitoring stack, back up your data, and choose when to upgrade Kubernetes versions.

​
Getting started

Follow Getting started to create a Cluster, connect with kubectl, and run your first Workload.

​
Shared responsibility

For the full breakdown of what Latitude.sh operates and what you operate across the Cluster lifecycle, see Shared responsibility.