Hey team! Hope you are doing great! I noticed that Flyte V2 runs tasks are scheduled and runs all in the same k8s namespace. Though I believe Flyte V1 runs tasks in separate namespace depending on project and domain and also separately to Flyte services. The question is - is it possible to keep Flyte1's behavior and schedule tasks in different namespaces?

Hi Denis, I believe that should be possible, cc @glamorous-carpet-83516 @faint-pilot-24699

Thank you! Is it possible to set up via config in the helm chart?

From what I understand this is currently under development: github.com/flyteorg/flyte/pull/7775 Implementation is ongoing

Yeah, I’m implementing that one. On the helm side you can change which namespace task pods run in, but not have one per project. What the settings service gives you is per project and domain values on the pods themselves: service account, labels, annotations, environment variables, and task resource requests and limits. It won’t give you separate namespaces, just per-project configuration inside the one you have.

I wonder if we should add support for namespaces or templating of some sort? For us it can be helpful to namespace things at scale.

Thank you, that's great! And back to the namespace thing --

On the helm side you can change which namespace task pods run in

- it allows to pick namespace different to one where flyte is running?

It will break the Secret injection behavior for now as our secret webhook assumes the task pods running in the same namespace due to k8s secret env reference limitation. We should think about how to solve this problem before supporting multi namespace.

For us it can be helpful to namespace things at scale

Big plus to this, having separate namespaces is very useful for us too