You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi! Thanks for setting up this helm chart repository, it helps get things up and running.
I'm not familiar with helm and I've been trying to understand how to embed secrets in my values.yaml file. I've been looking into this for some time, but I haven't figured it out just yet. In particular, I'm having a hard time with how to provide a opsdroid.configuration value in my values.yaml which would contain secrets.
Here's the steps I did.
I added a secrets.yaml file with all the secret values I want to add to my opsdroid configuration, such as datadog api key, aws access key, etc... The secrets file is created with helm secrets encrypt and it's working correctly (the secrets are correctly propagated to kubernetes and are available in the pod as env variables).
I changed the templates/opsdroid-secrets.yaml to be as follows:
This bit seems to be working correctly, as the env vars are propagated to the pod.
What doesn't work is the following configuration part:
...
configuration: |
# Here is my actual opsdroid configuration, which needs to refer to the secrets
logging:
...
welcome-message: false
connectors:
slack:
app-token: "....what do I put here to refer to the secrets?"
...
Nothing I tried works, which seems to suggest I need to change approach, but how?
Any suggestions would be welcome, as I've been struggling with this for a few hours now.
Hi! Thanks for setting up this helm chart repository, it helps get things up and running.
I'm not familiar with helm and I've been trying to understand how to embed secrets in my
values.yaml
file. I've been looking into this for some time, but I haven't figured it out just yet. In particular, I'm having a hard time with how to provide aopsdroid.configuration
value in myvalues.yaml
which would contain secrets.Here's the steps I did.
I added a
secrets.yaml
file with all the secret values I want to add to my opsdroid configuration, such as datadog api key, aws access key, etc... The secrets file is created withhelm secrets encrypt
and it's working correctly (the secrets are correctly propagated to kubernetes and are available in the pod as env variables).I changed the
templates/opsdroid-secrets.yaml
to be as follows:Originally, this template is instead doing something that I don't understand:
it seems to be referring to the environment variables defined in values? How would that work?
Are there any examples of this?
values.yaml
references to the secrets I just created, as follows:This bit seems to be working correctly, as the env vars are propagated to the pod.
What doesn't work is the following configuration part:
Nothing I tried works, which seems to suggest I need to change approach, but how?
Any suggestions would be welcome, as I've been struggling with this for a few hours now.
Thanks @jacobtomlinson !
The text was updated successfully, but these errors were encountered: