Soft multi-tenancy can be hard to achieve and secure. Multiple tenants sharing the same cluster means there are global objects, like Custom Resource Definitions (CRDs), namespaces, and so on, that you don’t want tenants controlling. You should separate platform admins, cluster admins, and tenants, with dedicated namespaces, role binding, node groups, taints and tolerations, etc.
Flux enforces tenant isolation by default, so you don’t have to worry about accidental tenant cross-contamination.
In this session, Priyanka “Pinky” Ravi, Developer Experience Engineer at Weaveworks, will walk you through how to set up multi-tenancy on an existing Kubernetes cluster and manage several tenants within the cluster.
Take advantage of the benefits that come with infrastructure as code.
⭐️ Flux website: fluxcd.io
⭐️ Flux Docs: fluxcd.io/flux
⭐️ Flux Multi-cluster setup:
⭐️ Additional Best Practices for Shared Cluster Multi-tenancy: ⭐️https://fluxcd.io/flux/security/best-practices/#additional-best-practices-for-shared-cluster-multi-tenancy
Requirements [10 words]: Must have a laptop, phone, or tablet to listen to the talk and see slides