https://deploy-preview-82--docs-projectcapsule.netlify.app/docs/guides/Recent content in Guides on CapsuleHugo -- gohugo.ioenhttps://deploy-preview-82--docs-projectcapsule.netlify.app/docs/guides/namespace-migration-across-tenants/Mon, 01 Jan 0001 00:00:00 +0000https://deploy-preview-82--docs-projectcapsule.netlify.app/docs/guides/namespace-migration-across-tenants/Capsule relays on two components to associate given namespace with tenant. Namespace’s OwnerReference.name pointing to the Tenant defintion Namespace’s OwnerReference.uid pointing to the Tenant defintion If a cluster administrator changes the Namespace by matching the other Tenant with the proper UID and name, the Namespace can be easily transferred. kubectl get tenants NAME STATE NAMESPACE QUOTA NAMESPACE COUNT NODE SELECTOR AGE solar Active 1 46s wind Active 1 39s Get tenant’s metadata.https://deploy-preview-82--docs-projectcapsule.netlify.app/docs/guides/use-fluxcd/Mon, 01 Jan 0001 00:00:00 +0000https://deploy-preview-82--docs-projectcapsule.netlify.app/docs/guides/use-fluxcd/Multi-tenancy the GitOps way This document will guide you to manage Tenant resources the GitOps way with Flux configured with the multi-tenancy lockdown. The proposed approach consists on making Flux to reconcile Tenant resources as Tenant Owners, while still providing Namespace as a Service to Tenants. This means that Tenants can operate and declare multiple Namespaces in their own Git repositories while not escaping the policies enforced by Capsule. Quickstart Install In order to make it work you can install the FluxCD addon via Helm: