rancher/rke

Rancher Kubernetes Engine (RKE), an extremely simple, lightning fast Kubernetes distribution that runs entirely within containers.

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 41 minutes ago
Added to GitGenius on April 7th, 2021
Created on October 25th, 2017
Open Issues & Pull Requests: 39 (+0)
Number of forks: 590
Total Stargazers: 3,294 (+0)
Total Subscribers: 121 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 5.3 days
Mean response time: 219.3 days
90th percentile: 798.4 days
Tracked items: 65

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 5
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 1,448 days
Stale 30+ days: 5
Stale 90+ days: 5

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • status/stale (55)
  • team/area2 (13)
  • team/infracloud (7)
  • kind/bug (6)
  • kind/enhancement (4)
  • area/automation (2)
  • area/rke (2)
  • internal (1)

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

RKE is a Kubernetes distribution that runs entirely within containers and installs via a simple command-line tool.

RKE solves the problem of deploying Kubernetes clusters across diverse infrastructure by packaging the entire distribution in containers, eliminating the need for complex host-level package management. The tool works by reading a cluster configuration file and orchestrating container-based Kubernetes components across your nodes, making deployment straightforward and reproducible regardless of the underlying operating system or cloud provider.

RKE suits teams that need to run Kubernetes on existing infrastructure without heavyweight installation procedures. It works well for on-premises deployments, multi-cloud scenarios, and environments where you control the underlying nodes. The project is reaching end of life, with version 1.8 as the final release in the 1.x series; users are encouraged to migrate to RKE2 for ongoing support and new features.

The project typically responds to issues and pull requests within one to two weeks. Development activity centers on infrastructure and cloud-related work, with the issue tracker dominated by bug reports and work from infrastructure-focused teams.