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

vCluster

vCluster - Create fully functional virtual Kubernetes clusters - Each vcluster runs inside a namespace of the underlying k8s cluster. It's cheaper than creating separate full-blown clusters and it offers better multi-tenancy and isolation than regular namespaces. observed · 2026-08-28

github.com/loft-sh/vcluster · 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: 4
  • age_days: 1973
  • days_rel: 26
  • days_push: 7
  • n_releases_24m: 84

Full methodology

Adoption not part of the score

11275 stars · 596 forks observed · 2026-08-28

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

vCluster is an open-source tool that creates fully functional virtual Kubernetes clusters, each running inside a namespace of an underlying host cluster, providing stronger multi-tenancy and isolation than plain namespaces at lower cost than separate full clusters. It has evolved into a broader tenant cluster platform for AI infrastructure, supporting managed Kubernetes, Slurm, and inference clusters on shared nodes, private nodes, or bare metal via its vMetal machine API.

Use cases

  • run isolated virtual kubernetes clusters inside a shared host cluster
  • give each team or customer their own kubernetes control plane without provisioning full clusters
  • build a multi-tenant kubernetes platform for internal teams or external customers
  • spin up ephemeral kubernetes clusters for local development and CI with Docker
  • offer self-service managed kubernetes on GPU infrastructure for AI workloads
  • achieve kubernetes multi-tenancy beyond namespaces with isolated API servers and RBAC
  • turn bare metal GPU servers into a cloud platform with tenant clusters

When to choose

  • you need hard isolation between tenants on a shared kubernetes cluster
  • creating separate full clusters per team or customer is too expensive or slow
  • you are building an AI cloud, GPU cloud, or platform-engineering offering with self-service clusters
  • you want a CNCF-certified kubernetes experience with your own API server, CRDs, and RBAC per tenant

When to avoid

  • simple namespaces with RBAC and resource quotas are sufficient isolation for trusted internal teams
  • you have no kubernetes cluster or infrastructure to host virtual clusters on
  • you need a fully managed hosted kubernetes service rather than self-operated tooling
  • your workloads are tiny and the overhead of a virtual control plane is not justified

Facets

application · maturity stable

container-orchestration cloud deployment microservices self-hosted developer-tools cloud-computing infrastructure-as-code self-hosted microservices go windows cli self-hosted cloud virtual-clusters multi-tenancy kubernetes tenant-isolation platform-engineering ai-infrastructure gpu-clouds helm k3s bare-metal containers devops docker linux macos

9 sources

Member repositories

RepositoryRoleHealth v2
loft-sh/vclustermain94
loft-sh/vindmirror54

For agents

markdown · JSON · MCP: product_card(name="loft-sh/vcluster")

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