Rancher’s k3k lets you spin up isolated K3s clusters inside an existing Kubernetes cluster via a Helm controller and a CLI tool.
Key Takeaways
Two modes: shared (resource-efficient, co-tenant) and virtual (dedicated K3s server pods per cluster, full isolation).
k3kcli cluster create mycluster provisions a cluster and outputs a ready kubeconfig in roughly 73 seconds based on example output.
Clusters are also declarable as k3k.io/v1beta1 Cluster CRDs, making them GitOps-friendly.
Requires an existing RKE2 cluster, Helm, and a default storage class; ephemeral or static storage supported as fallback.
Native Rancher UI integration for monitoring and scaling embedded clusters.
Hacker News Comment Review
The dominant reaction is that k3k duplicates vCluster (loft-sh/vcluster), an established OSS tool doing the same job, raising questions about differentiation.
With only two comments, there is no technical depth discussion on performance, security boundaries, or shared-vs-virtual mode tradeoffs yet.
Notable Comments
@redrove: flags k3k as functionally equivalent to vCluster, Rancher-branded.
