Hi team… we’re having a bit of an issue with Secrets as documented 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.

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

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/<group_name>/my_token.. instead of MY_TOKEN

yes, keys should be lower case sorry

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

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

using lowercase fixed the issue

@Smriti Satyan, let’s update the secret docs.