cool-waitress-85601
04/01/2026, 1:41 PMancient-wolf-19325
04/01/2026, 1:41 PMlimit-namespace field in the propeller configuration to the desired namespace name. For example, in propeller-config.yaml, use limit-namespace: "<your-namespace>". This restricts FlytePropeller to only process workflows in that namespace. By default, limit-namespace is set to "all", which means all namespaces are watched.
See the relevant configuration example in flytepropeller/propeller-config.yaml for details.
Would you like more detail on how to apply or update this configuration?
Sources:
- flytepropeller/propeller-config.yaml 👍 0 button 👎 0 button 💡 Hint: Mention @runllm in the thread for followups.cool-waitress-85601
04/01/2026, 1:42 PMancient-wolf-19325
04/01/2026, 1:42 PMflyte):
configmap:
core.yaml: |
propeller:
limit-namespace: flyte
This ensures FlytePropeller only watches the flyte namespace, as shown in the core.yaml section of the Helm chart configmap in flyte_helm_dataplane_generated.yaml.
Would you like more detail on where to place this in your deployment?
Sources:
- flyte_helm_dataplane_generated.yaml 👍 0 button 👎 0 button 💡 Hint: Mention @runllm in the thread for followups.