Secrets not working on Kubernetes cluster

[ivor-grisel]

Describe the issue

Setup:

• Github repo, which is used by >
• ArgoCD to deploy Kestra
• Everything runs on an AWS EKS cluster

I've used the following files:

• values.yaml defined here: https://github.com/kestra-io/helm-charts/blob/master/charts/kestra/values.yaml. With the addition of the value extraSecretEnvFrom as described here: https://kestra.io/docs/how-to-guides/kubernetes-secrets (and everything is copy paste from these pages)
• Dependency in the Chart.yaml is set to the latest version (0.18.0)
• The flow as defined here: https://kestra.io/docs/how-to-guides/kubernetes-secrets (again, copy & paste)

The end result, when executing this flow, doesn't show any information in regards to password and username (seen screenshot next post) (edited)

Environment

• Kestra Version: 0.18.0 (or at least, that's the Helm chart that I'm using)
• Operating System (OS/Docker/Kubernetes): AWS, Kubernetes
• Java Version (if you don't run kestra in Docker):

Additional info:

• This was a clean install of Kestra. So literally copy & paste of the above files
• Not sure if Docker in Docker is necessary, but that is running "as-is" in the values.yaml. If root in Docker was necessary, that was unclear from the documentation

Importance

We are currently looking at Kestra to replace our managed file transfer solution. We are not a paying customer yet. This is just something that I noticed. From my end, the priority of this is quite low, as we can test Kestra without it working.

[Ben8t]

@paulgrainger85 do you see anything wrong going on here 🤔 ?

[paulgrainger85]

I can't see anything obviously wrong - is it possible to share the config of the service you have created, along with a mock-up of the secrets you've applied? I have followed the instructions above myself and the secret is picked up as expected