# Install vcluster with Homebrew, Nix, scoop, winget Creates fully functional virtual k8s cluster inside host k8s cluster's namespace. Version 0.35.1 via Homebrew; verified 2026-06-22. ## Install ```sh sudo av install brew:vcluster ``` Additional install commands: ### macOS - Homebrew (100%): ```sh brew install vcluster ``` Evidence: local Homebrew formula metadata ### Linux - Nix (92%): ```sh nix profile install nixpkgs#vcluster ``` Evidence: nixpkgs package indexes: pkgs/by-name/vc/vcluster/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1 ### Windows - Scoop (92%): ```sh scoop install main/vcluster ``` Evidence: Scoop official bucket manifest trees: bucket/vcluster.json from https://api.github.com/repos/ScoopInstaller/Main/git/trees/master?recursive=1 - winget (92%): ```sh winget install --id loft-sh.vcluster -e ``` Evidence: Windows Package Manager source index: loft-sh.vcluster from https://cdn.winget.microsoft.com/cache/source.msix ## Package facts - **Package key:** brew:vcluster - **Package manager:** Homebrew - **Package manager page:** - **Version:** 0.35.1 - **Source summary:** Creates fully functional virtual k8s cluster inside host k8s cluster's namespace - **Homepage:** - **Repository:** - **Upstream docs:** - **License:** Apache-2.0 - **Source archive:** - **Last updated:** 2026-06-22T15:19:59Z - **Generated:** 2026-07-08T07:18:31+00:00 ## Executables - vcluster (cli) - vcluster (alias) ## Dependencies - helm - kubernetes-cli ## Build dependencies - go ## Install behavior - Post-install hook: not defined - Bottle: available on arm64_linux, arm64_sequoia, arm64_sonoma, arm64_tahoe, sonoma, x86_64_linux ## Freshness - Page generated: 2026-07-08 - Package-manager version: 0.35.1 - Package-manager updated: 2026-06-22 - Local data: ok - Upstream repository: https://github.com/loft-sh/vcluster - Upstream latest detected: v0.35.1 (current) ## Project history and usage vcluster is Loft Labs' open-source tool for creating virtual, tenant-oriented Kubernetes clusters. Instead of giving every team a full physical or cloud cluster, vcluster runs an isolated Kubernetes control plane and syncs selected resources onto underlying infrastructure. ### Project history Loft Labs introduced vcluster as a response to Kubernetes multi-tenancy tradeoffs: namespace-only isolation can be too weak for teams that need their own CRDs and admin-like control, while one physical cluster per tenant is expensive and operationally heavy. A Loft-authored 2022 article describes virtual clusters as a model that combines the tenant experience of a dedicated cluster with the cost profile of shared infrastructure. A May 12, 2022 Loft Labs announcement says vcluster was first launched in April 2021 and had grown to more than 3 million downloads and over 1,500 GitHub stars in less than a year. The same announcement positions vcluster as a lightweight cluster running inside namespaces of underlying Kubernetes clusters and notes CNCF conformance certification. ### Adoption history vcluster's adoption followed platform-engineering and cloud-native multi-tenancy needs: development environments, ephemeral CI/CD clusters, internal developer platforms, customer environments, and later GPU and AI infrastructure. The GitHub README now presents it as production Kubernetes and AI infrastructure for tenant clusters, with Kubernetes certification, more than 11,000 GitHub stars, and public customer references. The project also expanded from the original shared-host-cluster model into multiple isolation profiles. The README and docs describe shared nodes, dedicated nodes, private nodes, Docker-based local clusters, and standalone operation, reflecting a shift from developer-platform convenience toward production tenant isolation. ### How it is used A common workflow is to run `vcluster create my-vcluster --namespace team-x`, connect kubectl to the virtual cluster, and let users install workloads as if they had a normal Kubernetes cluster. The virtual cluster can expose its own API server, CRDs, RBAC, and namespace view while the host cluster schedules or hosts the underlying resources. Configuration is commonly expressed in `vcluster.yaml`, where users choose sync behavior, node isolation, service exposure, private nodes, standalone mode, and integrations. The design-principles documentation emphasizes low overhead, few host-cluster API requests, flexible deployment by CLI/Helm/Terraform, no cluster-admin requirement for basic deployment, and single-namespace encapsulation. ### Why package nerds care vcluster is package-nerd significant because it gives a single CLI the feel of `kind` or `minikube` while targeting a harder production problem: many Kubernetes tenants sharing or virtualizing infrastructure without copying a full cluster for each one. For package managers, it is also a moving cloud-native binary with a fast release train and a YAML-centered workflow. Installing `vcluster` gives developers a portable local and remote control-plane tool that composes with kubectl, Helm, Argo CD, Crossplane, Terraform, and Cluster API-style platform workflows. ### Timeline - 2021-04: Loft Labs first launches vcluster, according to its 2022 announcement. - 2022-03-29: Opensource.com publishes Loft's overview of virtual Kubernetes clusters and vcluster's multi-tenancy model. - 2022-05-12: Loft Labs announces a Cluster API provider for vcluster and reports more than 3 million downloads. - 2026-06: GitHub release data shows v0.35.1 published, while the docs list v0.35 as the stable documentation version. - 2026-07-02: GitHub release data shows v0.36.0-alpha.1, indicating active pre-release development after v0.35. ### Related projects - Kubernetes is the substrate and API model that vcluster virtualizes. - kubectl, Helm, Terraform, Argo CD, Crossplane, and Cluster API are common companion tools in vcluster workflows. - kind and minikube are adjacent local-cluster tools, while vcluster's niche is tenant clusters and virtual control planes on shared or dedicated infrastructure. - Loft Labs' related platform projects and integrations include vCluster Platform, vNode, vMetal, Netris integration, and the Docker-based `vind` driver. ### Sources - - - - - - - ## Security Notes infrastructure mutation or orchestration signal. - **Geiger risk:** orange / medium - infrastructure mutation or orchestration signal ## Configuration and credential file locations These source-backed paths show where this package keeps local settings or durable credentials. Automic Vault can use them as review targets for secret scanning, migration, and command approval. ## Configuration files - Unix: vcluster.yaml, /etc/vcluster/vcluster.yaml, /var/lib/vcluster/config.yaml ## Source Database Details - **Source Database:** Homebrew formula API - **Tap:** homebrew/core - **Full Name:** vcluster - **Version Scheme:** 0 - **Revision:** 0 - **Head Version:** HEAD - **Bottle Stable Root URL:** - **Deprecated:** no - **Disabled:** no - **Keg Only:** no - **URL Keys:** head, stable ## Other Package-Manager Records - Nix - vcluster: normalized package name match | nixpkgs package indexes: pkgs/by-name/vc/vcluster/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1 - Scoop - main/vcluster: normalized package name match | Scoop official bucket manifest trees: bucket/vcluster.json from https://api.github.com/repos/ScoopInstaller/Main/git/trees/master?recursive=1 - winget - loft-sh.vcluster: normalized package name match | Windows Package Manager source index: loft-sh.vcluster from https://cdn.winget.microsoft.com/cache/source.msix ## Related links - [Cloud CLI packages](https://www.automicvault.com/pkg/cloud-clis/) - Belongs to a cloud or infrastructure command family. - [Secret-risk packages](https://www.automicvault.com/pkg/secret-risk-packages/) - Has protected-tool coverage, approval-gate, or non-low Geiger security signals. - [Terminal utility packages](https://www.automicvault.com/pkg/terminal-utilities/) - Matched terminal and command-line workflow metadata. - [Networking and protocol packages](https://www.automicvault.com/pkg/networking-protocol-tools/) - Matched network, protocol, or remote-service metadata. - [helm](https://www.automicvault.com/pkg/brew/helm/) - Runtime dependency declared by Homebrew. - [kubernetes-cli](https://www.automicvault.com/pkg/brew/kubernetes-cli/) - Runtime dependency declared by Homebrew. - [go](https://www.automicvault.com/pkg/brew/go/) - Build dependency declared by Homebrew. - [uffizzi](https://www.automicvault.com/pkg/brew/uffizzi/) - Shares av.db curated category or tags: cli, cloud-infrastructure, kubernetes, virtual-clusters. - [cdk8s](https://www.automicvault.com/pkg/brew/cdk8s/) - Shares av.db curated category or tags: cli, cloud-infrastructure, kubernetes. - [chaoskube](https://www.automicvault.com/pkg/brew/chaoskube/) - Shares av.db curated category or tags: cli, cloud-infrastructure, kubernetes. - [click](https://www.automicvault.com/pkg/brew/click/) - Shares av.db curated category or tags: cli, cloud-infrastructure, kubernetes. - [cloud-provider-kind](https://www.automicvault.com/pkg/brew/cloud-provider-kind/) - Shares av.db curated category or tags: cli, cloud-infrastructure, kubernetes. - [clusterawsadm](https://www.automicvault.com/pkg/brew/clusterawsadm/) - Shares av.db curated category or tags: cli, cloud-infrastructure, kubernetes. - [clusterctl](https://www.automicvault.com/pkg/brew/clusterctl/) - Shares av.db curated category or tags: cli, cloud-infrastructure, kubernetes. - [cozyhr](https://www.automicvault.com/pkg/brew/cozyhr/) - Shares av.db curated category or tags: cli, cloud-infrastructure, kubernetes. - [kops](https://www.automicvault.com/pkg/brew/kops/) - Local package facts share a topical domain. Shared terms: cli, cloud, cloud-infrastructure, cluster, infrastructure. - [devspace](https://www.automicvault.com/pkg/brew/devspace/) - Local package facts share a topical domain. Shared terms: cli, cloud, cloud-infrastructure, infrastructure, k8s. ## Combined YAML source View the package source record on GitHub. [combined/vcluster.yml](https://github.com/automic-vault/db/blob/main/combined/vcluster.yml) ## Sources - Nucleus package database - Geiger risk classifier - package-page enrichment - curated configuration and credential file locations - curated package history - package version freshness - av.db category and tag curation - package relationship graph - external package-manager database matches - cross-ecosystem install command graph