Hi team we re having a bit of an issue with Secrets as docum

Question

Hi team we re having a bit of an issue with Secrets as documented <https docs flyte org projects cookbook en stable auto core containerization use secrets html|here> After following the steps we see a new secret named `flyte pod webhook` instead of `flyte pod webhook secret` Is this expected End result the pod running the task is unable to actually access the secrets and fails

Yee · Answer

hey i think that s not a huge problem though we should correct the name in the docs looking at our internal test deployment of flyte these are the only two we see ```flyte flyte pod webhook Opaque 3 214d flyte flyte pod webhook token gtfrr <http kubernetes io service account token|kubernetes io service account token> 3 214d```

Yee · Answer

can you copy paste here the labels annotations for the task pod the task that s supposed to get the secret

Rupsha Chaudhuri · Answer

do you expect the keys to be lower case I have a key defined as MY TOKEN then the task complains because it can t find etc flyte secrets lt group name gt my token instead of MY TOKEN

Yee · Answer

yes keys should be lower case sorry

Yee · Answer

this has been fixed but not released yet 1 2 Flyte release

Rupsha Chaudhuri · Answer

aha that s probably our final issue that we need to solve Can you please update the docs

Rupsha Chaudhuri · Answer

ah I see

Yee · Answer

we do need to amend our docs to explicitly say that secrets are not case sensitive

Yee · Answer

as in you can t have a secret MY SECRET and a different secret my secret that will cause weird undefined behavior in Flyte We should probably put in an issue in flyte to have that raise an error

Rupsha Chaudhuri · Answer

using lowercase fixed the issue

Samhita Alla · Answer

< Smriti Satyan> let s update the secret docs