👋 We deploy flyte on GKE via the helm chart and I am trying to pass a secret value to flytepropeller so it can effectively set

--propeller.resourcemanager.redis.hostKey

but without needing to pass the value on the command line (so the secret is actually hidden) or keep it in a non-secret config map. Does flytepropeller support environment variables for adding on to the default config values (so I could just set something like

FLYTE_PROPELLER_RESOURCEMANAGER_REDIS_HOSTKEY

) in a secret and mix it into the flytepropeller deployment, or would this need to be more involved (update the actual code for flytepropeller to read from a kubectl secret / env var)? I am hoping I am just missing something obvious 😅

assuming this is

flyte-core

I think you can inject those envvars here: https://github.com/flyteorg/flyte/blob/ba88e82a58145fe3062c7441cdd5c57c36f108f2/charts/flyte-core/values.yaml#L340-L341

Thanks, we can certainly get them into the container that way, but my tests showed that flytepropeller wasn't using that env var, but I can't figure out for the life of me what env var it would use or if that is even supported

Now I get it, sorry I don't see a way, I just see how whatever you set in the values file goes straight to the configmap. In this case maybe adding to

helpers.tpl

a routine that would let users specify a secret would be necessary