rancher/k3k

Kubernetes in Kubernetes

Owned by SUSE

View on GitHub ↗Jump to charts ↓

rancher/k3k has 900+ stars and 80+ forks on GitHub, is written in Go, and was last pushed on Oct 15, 2026. Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 23 minutes ago
Added to GitGenius on October 12th, 2026
Created on January 18th, 2023
Open Issues & Pull Requests: 117 (+0)
GitHub issues: Enabled
Number of forks: 89
Total Stargazers: 920 (+0)
Total Subscribers: 8 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 4.8 days
Mean response time: 40.1 days
90th percentile: 119.5 days
Tracked items: 333

Maintainer activity

20 people did triage or write work on this repository in the last 12 months.

Counts unlabeled, assigned, unassigned, milestoned, demilestoned, locked, unlocked over the last 12 months. These are issue and pull request events that require triage or write permission. Commits and code review are not counted. labeled and renamed are excluded because GitHub issue forms record the issue author as the actor. Figures from October 18, 2026. This count is not comparable across projects: each project's automation decides which of these events a person emits. How this is counted.

How this project is maintained

About 19% of issues opened in the past year have never received a reply. 43% of open issues come from outside the core team, a mix of external reports and the maintainers' own roadmap. Work labelled "bug" is answered fastest, typically in under an hour, while "documentation" waits about 5 weeks. Almost all tracked open issues have seen activity in the last three months. Only 54% of issues opened in the past year have been closed.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 96
New in 7 days: 2
Closed in 7 days: 0
Avg open age: 232 days
Stale 30+ days: 41
Stale 90+ days: 5

Recent activity

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

Top labels

  • team/collie (124)
  • bug (63)
  • enhancement (49)
  • virtual-kubelet (28)
  • good first issue (24)
  • controller (18)
  • QA/none (17)
  • QA/S (16)

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

K3k is a tool for running Kubernetes clusters within an existing Kubernetes environment.

K3k addresses the challenge of running multiple isolated Kubernetes clusters on shared infrastructure without the overhead of managing separate physical machines. It works by deploying lightweight K3s clusters as workloads inside a parent Kubernetes cluster, with two operational modes: shared mode optimizes resource utilization by allowing clusters to share underlying resources, while virtual mode provides stronger isolation by giving each embedded cluster dedicated control plane and node pods. This approach enables efficient multi-tenancy, supports experimentation and testing workflows, and reduces infrastructure costs by consolidating multiple clusters onto the same physical host.

Organizations should consider K3k when they need to provide isolated Kubernetes environments to multiple teams or projects without managing separate physical infrastructure, or when they want to streamline development and testing by quickly spinning up and tearing down temporary clusters. The tool suits scenarios requiring resource isolation with defined quotas and limits, simplified access control through separate RBAC configurations, and rapid cluster provisioning. K3k integrates with Rancher for centralized management of embedded clusters. Teams prioritizing maximum resource efficiency should use shared mode, while those needing stronger workload isolation should use virtual mode, though virtual mode currently requires privileged agent pods on the host node unless a sandboxed runtime like Kata Containers is configured.

The project maintains active test coverage including conformance tests for both virtual and shared modes. Development activity shows consistent attention to build and release processes with automated workflows for testing and releases.