This repo is the GitOps and use-case template for vCluster Platform demos.

Use one of these entrypoints:

• managed: vcluster-platform-demo-generator.md
• self-managed host cluster: self-managed-demo-cluster/README.md
• self-contained vind: vind-demo-cluster/README.md

If you want the shortest path, use vind:

LICENSE_TOKEN="$TOKEN" bash vind-demo-cluster/bootstrap-self-contained.sh

Default vind values:

• Forgejo org: vcluster-demos
• Forgejo repo: vcp-gitops
• demo image: pushed to forgejo.vcp.local/vcluster-demos/vcp-gitops/vcp-gitops-demo-app
• local URLs:
  • https://vcp.local
  • https://argocd.vcp.local
  • https://forgejo.vcp.local
• cluster shape: 1 control plane node, 2 worker nodes

Main repo areas:

• vcluster-gitops/: Platform GitOps content, Argo CD bootstrap, projects, teams, secrets, templates
• vcluster-use-cases/: demo use cases
• vind-demo-cluster/: self-contained vind bootstrap
• scripts/: local helper scripts
• docs/self-service-enablement/README.md: enablement demo flow for self-service provisioning, project multi-tenancy, and RBAC
• docs/secret-contract.md: secret contract for ESO / 1Password

vCP Free below is based on the official feature comparison and free-tier overview:

• Compare pricing tiers
• vCluster Free announcement

Yes means the use case maps to features explicitly called out as available in the Free plan. Enterprise means it depends on features documented outside the Free plan. Depends means the repo example is mostly built from apps, templates, or external tooling and is not mapped cleanly to one specific line item in the pricing table.

vind above is the current self-contained OrbStack-backed path:

• Yes means the use case has been validated on vind
• TBD means it has not been fully validated on vind yet
• No* means the overlay code exists but the use case is temporarily disabled due to an upstream blocker

Both the Demo Generator path and the self-contained vind path use the Argo CD cluster secret named cluster-local in namespace argocd to decide which use-case ApplicationSets should match the local management cluster.

That means you can enable or disable use cases directly with kubectl label without rerunning the full bootstrap.

Example:

kubectl -n argocd label secret cluster-local \
  eso=true \
  autoSnapshots=true \
  flux=true \
  crossplane=false \
  rancher=false \
  --overwrite

Disable a use case:

kubectl -n argocd label secret cluster-local customResourceSync=false --overwrite

Enable a few more use cases with the exact label keys:

kubectl -n argocd label secret cluster-local \
  argoCdInVcluster=true \
  customResourceSync=true \
  cnpg=true \
  connectedHostCluster=true \
  namespaceSync=true \
  privateNodes=true \
  resolveDNS=true \
  tenantObservability=true \
  virtualScheduler=true \
  --overwrite

Typical flow:

1. connect kubectl to the demo environment management cluster
2. update one or more labels on argocd/cluster-local
3. wait for Argo CD to refresh the matching ApplicationSets and Applications

The label keys currently used by the repo are:

Additional behavior toggle:

Notes:

• on the vind path, the bootstrap --use-cases flag writes these labels for you
• on the vind path, cnpg is derived automatically when either database-connector or custom-resource-sync is enabled
• if you edit argocd/cluster-local manually, set cnpg=true whenever either databaseConnector=true or customResourceSync=true
• on the vind self-contained path, legacyArgoKargo is derived automatically when continuous-promotion is enabled without flux, so you do not need to set that label by hand
• on the Demo Generator path, the initial values usually come from template parameters and the generated cluster secret
• changing the secret directly is the fastest way to test another combination after the environment already exists

For the self-contained path, the Argo CD root app is:

• root-application.yaml

The self-contained Git overlay is:

• vcluster-gitops/overlays/local-contained/README.md