Question regarding the `limit-namespace` option for propeller: I've tried to reverse engineer the semantics from the code, but I've wanted to verify. Is it possible to pass a list of allowed namespaces here, or is it limited to just

all

or a single namespace? Based on how the information is used in `controller.go` , line 516, I fear that only a single namespace is allowed, right? If so, would you consider using something like xns-informer (Github) to allow a list instead? My use case: I'm trying to deploy multiple instances of the Flyte control plane in a single cluster for review during CI runs of a deployment configuration. Having multiple propellers configured with

limit-namespace=all

causes a race condition between them. Limiting each propeller instance to a single workflow namespace is too narrow OTOH, since in my understanding it precludes the use of k8s namespaces to separate Flyte projects (please correct me if I'm wrong here). Thanks for your help! 🙏

Great question @Adrian Rumpold! Yes, currently the

limit-namespace

configuration option only allows a single value. However, you might want to look into propeller manager. Basically, this component is meant for managing deployments with multiple propeller instances, and rather than limiting the informer to only watch a certain namespace it uses label selectors to include / exclude certain Flyte project / domains. So if you're able to partition the CI runs by project or domain you can either (1) use the propeller manager to automatically manage multiple propeller instances or (2) manually add include / exclude project / domain label selectors to each individual propeller deployment to fit your needs.

Thanks for your answer, @Dan Rammer (hamersaw)! From skimming the page, propeller manager sounds exactly like what I was looking for! I'll try it out and see how far I can get 🙂