Cloud Parts

Rancher

SUSE’s open-source control plane for fleets of Kubernetes clusters: one place to create, import, secure and upgrade them.

What it is
Container orchestration
Part of
Tool for Kubernetes
Type
Open source
Made by
SUSE
License
Apache 2.0 (Rancher Prime is a paid subscription)
Facts checked
6 October 2026
Website Source code

What it is

Rancher is itself a Kubernetes application. You install it with Helm onto a small Kubernetes cluster (the “local” cluster), and it then manages any number of “downstream” clusters. It can create them (RKE2 or K3s on VMs or bare metal it provisions through cloud drivers, or hosted EKS, AKS and GKE clusters through their APIs) or import any existing conformant cluster. In each downstream cluster a cattle-cluster-agent opens a tunnel back to the Rancher server, so the connection starts from inside each managed cluster.

On top of that link Rancher adds what plain Kubernetes leaves to you across many clusters: one login backed by Active Directory, GitHub, Okta or other identity providers, an authentication proxy that impersonates each user on the target cluster, RBAC templates and “projects” (groups of namespaces) applied everywhere, a web UI, a Helm app catalog, Fleet for GitOps deployments to many clusters at once, and Prometheus-based monitoring. For RKE2 and K3s clusters it also handles Kubernetes upgrades and etcd snapshots through an agent on every node.

Why teams pick it

  • Manages almost any cluster: ones it creates, hosted EKS, AKS and GKE, and imported clusters from any conformant distribution
  • Central identity and RBAC: users log in once and get consistent permissions on every cluster
  • Agents open the connection from inside each cluster, which suits clusters at the edge, behind NAT or in other clouds
  • The full platform is open source under Apache 2.0 and free to run; Prime adds support, not a different codebase

Watch out for

  • Rancher is one more critical system to run, back up and upgrade; for production it should sit on its own HA Kubernetes cluster
  • Deepest integration is with SUSE’s own RKE2 and K3s; imported and hosted clusters get fewer lifecycle features
  • Recent patch releases for older minor lines (such as v2.14.5 in August 2026) shipped as Prime builds, so community users need to track the newest minor version
  • Longer support windows, signed images with SBOMs from a trusted registry and SUSE support require a Rancher Prime subscription

More of the Kubernetes family

What all container orchestration have in common →
kubeadmOpen sourceToolsThe official tool for turning Linux machines you already have into a Kubernetes cluster: `kubeadm init`, then `kubeadm join`.Amazon EKSAWSManaged servicesAWS runs the Kubernetes control plane for you; you choose how much of the worker side to hand over too.Azure Kubernetes ServiceAzureManaged servicesMicrosoft’s managed Kubernetes: a control plane that can be free, node pools of Azure VMs, and an Automatic mode that runs the nodes too.Google Kubernetes EngineGoogle CloudManaged servicesGoogle’s managed Kubernetes, the oldest one: Google runs the control plane, and in Autopilot mode the nodes too.K3sOpen sourceDistributionsA certified Kubernetes distribution in one small binary, built for edge, IoT and other places where a full cluster is too heavy, with SQLite or embedded etcd for state.MicroK8sOpen sourceDistributionsCanonical’s Kubernetes in one snap package: installs with one command on Linux, forms a highly available cluster by itself at three nodes, and adds features as addons.Red Hat OpenShiftCommercialDistributionsRed Hat’s Kubernetes platform: Kubernetes plus its own OS, operators that install and upgrade everything, and stricter security defaults, sold by subscription.RKE2Open sourceDistributionsSUSE’s security-focused Kubernetes distribution: one binary per node, hardened defaults, FIPS-validated crypto and close alignment with upstream.Talos LinuxOpen sourceDistributionsA Linux distribution that only runs Kubernetes: immutable, minimal, with no shell or SSH, and managed entirely through an API.kindOpen sourceFor local developmentKubernetes IN Docker: each cluster node is a container, so a conformant multi-node cluster starts and disappears inside a CI job.minikubeOpen sourceFor local developmentA local Kubernetes cluster for developers on Linux, macOS or Windows, in a container, a VM or on the host itself, with laptop-friendly extras.AgonesOpen sourceBuilt on itRuns dedicated multiplayer game servers on Kubernetes: keeps a fleet of them warm, hands one to each match, and never kills a server while players are on it.KlutchOpen sourceBuilt on itA young open-source control plane, built on Crossplane, that lets many application clusters order databases from one central Kubernetes cluster.

How it fits with other technologies

Install Rancher on an existing Kubernetes cluster with Helm · bash

helm repo add rancher-stable https://releases.rancher.com/server-charts/stable
kubectl create namespace cattle-system

# cert-manager must be installed first for Rancher-generated certificates
helm install rancher rancher-stable/rancher \
  --namespace cattle-system \
  --set hostname=rancher.my.org \
  --set bootstrapPassword=admin

kubectl -n cattle-system rollout status deploy/rancher

See it in a real stack

No architecture uses Rancher yet. Drop it into the playground and wire it up yourself.Open playground →
Where it came from2014–2025

Rancher Labs was founded in Cupertino in 2014 by Sheng Liang, Shannon Williams, Darren Shepherd and Will Chan. Docker had just made containers easy to build and run on one machine, but running them across many machines was still unsolved, and there was no clear winner among orchestrators. Rancher 1.0, released in March 2016, hedged: it shipped its own orchestrator, Cattle, and could also set up Kubernetes or Docker Swarm environments.

As Kubernetes pulled ahead of the other orchestrators, Rancher 2.0 (May 2018) was redesigned around it. Instead of being one more orchestrator, Rancher became a manager of many Kubernetes clusters, including EKS, AKS and GKE ones, with its own installer, RKE. The company then built K3s (2019) for the edge and RKE2 (2020) for regulated datacenters. SUSE agreed to buy Rancher Labs in July 2020 and closed the deal on December 1, 2020.

Under SUSE, Rancher stayed Apache-licensed, and SUSE sells it as Rancher Prime: the same code with support, longer lifecycles and a trusted image registry. RKE1, the Docker-based installer from 2.0, reached end of life in July 2025.

Why it’s built this way

Run the management server on Kubernetes itself
From 2.0, the Rancher server is built on an embedded Kubernetes API server and etcd, and stores its own objects as Kubernetes resources. Its controllers then work like any other Kubernetes controller, reconciling desired and actual state of downstream clusters.
Agents dial home
Each downstream cluster’s agent opens a tunnel to the Rancher server rather than Rancher reaching in, so a cluster only needs to be able to reach Rancher, which suits clusters behind firewalls or NAT and at the edge.
Manage other people’s Kubernetes too
Rather than insist on its own distribution, Rancher 2.0 shipped integrations for GKE, EKS and AKS and could import any cluster, betting that companies would end up with several kinds of Kubernetes and need one place to govern them.

Timeline

  1. 2014

    Rancher Labs founded; the rancher/rancher repository is created in November

  2. 2016

    Rancher 1.0 GA in March, with Cattle, Kubernetes and Swarm environments

  3. 2018

    Rancher 2.0 in May, redesigned to manage many Kubernetes clusters

  4. 2019

    K3s released for edge and small clusters

  5. 2020

    SUSE agrees to buy Rancher Labs in July and completes the deal on December 1

  6. 2021

    Rancher 2.6 provisions RKE2 clusters

  7. 2025

    RKE1 reaches end of life; Rancher 2.12 stops managing RKE1 clusters

Sources10 · facts checked 6 October 2026

Improve this page on GitHub