#3752 Flyte namespace hardcoded in Configmap Pull request opened by npapapietro Describe your changes Flyte helm charts allow the install into a specific namespace other than

flyte

. This works for all resources except in one spot. The propeller leader election is looking for a confmap in the flyte namespace regardless of if we install into that namespace. • Changes I've made are removing the

namespace

hard code from the

values.yaml

spots. • Added a

fromYaml

merge to that key based on the target namespace Check all the applicable boxes ☑︎ I updated the documentation accordingly. ☑︎ All new and existing tests passed. ☑︎ All commits are signed-off. Screenshots Note to reviewers flyteorg/flyte GitHub Actions: docs GitHub Actions: trigger-sandbox-lite-build GitHub Actions: compile GitHub Actions: trigger-sandbox-build ✅ 4 other checks have passed 4/8 successful checks