Ross ROSS = Recommend OSS · open-source software intelligence for agents

rancher/rke2

None observed · 2026-08-28

github.com/rancher/rke2 · homepage · Go · Apache-2.0 (permissive) observed · 2026-08-28

Health v2 · maintenance only

94/100

  • Activity 99
  • Release rhythm 84
  • Longevity 100
How is this computed?

round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10) — computed 2026-09-03. Adoption (stars, forks) is never an input.

  • gap_med: 0
  • age_days: 2339
  • days_rel: 29
  • days_push: 7
  • n_releases_24m: 100

Full methodology

Adoption not part of the score

2325 stars · 353 forks observed · 2026-08-28

What it is AI-extracted, prompt v1, taxonomy v1, 2026-08-30, confidence not recorded

RKE2 (RKE Government) is Rancher's fully conformant, next-generation Kubernetes distribution focused on security and compliance, particularly for the U.S. Federal Government sector. It combines K3s's ease of deployment with RKE1's upstream alignment, using containerd as the embedded runtime and offering CIS Benchmark defaults, FIPS 140-2 compliance, and SELinux/MCS support.

Use cases

  • deploy a secure kubernetes cluster on linux servers
  • run kubernetes that passes the CIS benchmark with minimal configuration
  • set up a FIPS 140-2 compliant kubernetes distribution
  • install kubernetes as a systemd service with a simple script
  • provision kubernetes clusters managed by Rancher
  • harden container images with CVE scanning in the build pipeline
  • replace RKE1 or K3s for datacenter kubernetes deployments

When to choose

  • you need a fully conformant kubernetes distribution with strong security and compliance defaults (CIS, FIPS, SELinux)
  • you want kubernetes that stays closely aligned with upstream rather than edge-optimized like K3s
  • you operate in government or regulated sectors with heightened security requirements
  • you want simple systemd-based installation and operation with Rancher integration

When to avoid

  • you need a lightweight edge or IoT kubernetes where K3s is more appropriate
  • you require FIPS compliance on Windows or s390x architectures
  • you want to run control plane components via Docker as in RKE1
  • you need a managed kubernetes service rather than self-hosted infrastructure

Facets

application · maturity active

container-orchestration security deployment self-hosted cloud-computing security infrastructure-as-code go self-hosted kubernetes-distribution rke2 rancher cis-benchmark fips selinux containerd government-compliance devops containers linux docker

4 sources

Member repositories

RepositoryRoleHealth v2
rancher/rke2main94

For agents

markdown · JSON · MCP: product_card(name="rancher/rke2")

Data as of 2026-08-30T08:39:29.467469+00:00 · Report a problem