After installing the helm chart - and everything was working great... secrets from workers are pulling in just fine from secrets in k8's. but then i noticed when I was using webhooks on ex: github resource - i started to see errors in the logs with for ex:
pipeline_name.secret_name .. the secrets are in the correct namespace and etc, but still a webhook being triggered wont work and its giving me that error in the logs.
So i decided to add the same secret but named it with the name of the pipeline.name_of_secret and it worked! why would i need to add the secret 2 times?
Reproduction steps
Install chart, add a secret , call it from a task. works fine and you can see it for ex: environment variable
add the same secret to webhook_token in git resource and trigger the webhook via curl command and you will get a 401 error. look at the kubectl logs and find pipeline_name.secret_name not found. create secret just like the one being asked and hit the webhook 1 more time. errors goes away and 200 success code.
Expected behavior
using the same secret a worker grabs from secrets in k8's vs. creating duplicates
Additional context
Sorry, i am the worst when it comes to writing these reports out :|
Describe the bug
After installing the helm chart - and everything was working great... secrets from workers are pulling in just fine from secrets in k8's. but then i noticed when I was using webhooks on ex: github resource - i started to see errors in the logs with for ex: pipeline_name.secret_name .. the secrets are in the correct namespace and etc, but still a webhook being triggered wont work and its giving me that error in the logs.
So i decided to add the same secret but named it with the name of the pipeline.name_of_secret and it worked! why would i need to add the secret 2 times?
Reproduction steps
Install chart, add a secret , call it from a task. works fine and you can see it for ex: environment variable add the same secret to webhook_token in git resource and trigger the webhook via curl command and you will get a 401 error. look at the kubectl logs and find pipeline_name.secret_name not found. create secret just like the one being asked and hit the webhook 1 more time. errors goes away and 200 success code.
Expected behavior
using the same secret a worker grabs from secrets in k8's vs. creating duplicates
Additional context
Sorry, i am the worst when it comes to writing these reports out :|