You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We want to deploy separate flux instance for every tenant, but it seems fluxcd-operator does not see any instances created outside of it's WATCH_NAMESPACE. How to make operator watch and handle FluxcdInstances from all namespaces?
So we probably need to write webhook which would automatically append the needed labels to created resources according to the namespace they were created.
Activity
stefanprodan commentedon Jun 26, 2024
Flux is not made to be deployed per namespace. You would set cluster.multitenant true. See here how multi-tenancy works https://fluxcd.io/flux/installation/configuration/multitenancy/
kvaps commentedon Jun 26, 2024
Got it. Can I target fluxcd to multiple namespaces?
Eg. one flux serves everything in
cozy-*Second for
tenant-user1andtenant-user1-extrakvaps commentedon Jun 26, 2024
There an option to use label selectors, eg.
--watch-label-selectorfor the controllers.https://fluxcd.io/flux/installation/configuration/sharding/
So we probably need to write webhook which would automatically append the needed labels to created resources according to the namespace they were created.
Is that correct way?
stefanprodan commentedon Jun 26, 2024
Why do you need sharding? Are you deploying 10K apps? Isn’t vertical scaling working for you?
For tentat isolation, you would only need to provision SA/RBAC in each namespace.
kvaps commentedon Jun 26, 2024
Not yet. We just want to enhance parallel resources processing and minimize the failure domain to specific tenants.