rancher/rke2

RKE2 is a Kubernetes distribution that emphasizes security and compliance for use within the U.S.

Owned by SUSE

View on GitHub ↗Jump to charts ↓Open shareable report →

rancher/rke2 has 2k+ stars and 350+ forks on GitHub, is written in Go, and was last pushed on Oct 17, 2026. Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 2 hours ago
Type:Server / PlatformCategory(s):Kubernetes & OperatorsCloud Native & Infrastructure
Added to GitGenius on October 12th, 2026
Created on April 7th, 2020
Open Issues & Pull Requests: 95 (+0)
GitHub issues: Enabled
Number of forks: 353
Total Stargazers: 2,370 (+0)
Total Subscribers: 70 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 0.0 hours
Mean response time: 13.4 days
90th percentile: 7.4 days
Tracked items: 1,864

How this project is maintained

About 3% of issues opened in the past year have never received a reply. 93% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. Work labelled "waiting-for-RC" is answered fastest, typically in under an hour, while "area/harvester" waits about 5 days. Almost all tracked open issues have seen activity in the last three months. 94% of issues opened in the past year have since been closed.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 55
New in 7 days: 25
Closed in 7 days: 26
Avg open age: 176 days
Stale 30+ days: 20
Stale 90+ days: 13

Recent activity

Opened in 7 days: 24
Closed in 7 days: 26
Comments in 7 days: 12
Events in 7 days: 43

Top labels

  • kind/backport (610)
  • area/cni (91)
  • kind/bug (43)
  • status/stale (41)
  • waiting-for-RC (29)
  • area/harvester (21)
  • kind/os-validation (21)
  • kind/upstream-issue (21)

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

RKE2 is a Kubernetes distribution that emphasizes security and compliance for use within the U.S. Federal Government sector.

The distribution solves the problem of deploying Kubernetes in environments with strict security and regulatory requirements. It achieves this by providing hardened defaults and configuration options designed to pass the CIS Kubernetes Benchmark with minimal operator intervention, enabling FIPS 140-2 compliance, supporting SELinux policy and Multi-Category Security label enforcement, and regularly scanning components for vulnerabilities using automated tooling in its build pipeline.

Organizations should adopt RKE2 if they operate in regulated environments where federal compliance standards apply or require high-security Kubernetes deployments. The tool is particularly suited for government agencies and enterprises with stringent security postures. The README distinguishes RKE2 from RKE1 and K3s, indicating these are the primary alternatives, though specific comparisons are not detailed in the provided materials.

The project maintains a release cadence aligned with upstream Kubernetes, targeting patch releases within one week and minor releases within thirty days. The versioning scheme directly reflects the upstream Kubernetes version with an RKE2-specific postfix, allowing multiple releases against the same upstream version while remaining semantically versioned.