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
I had some issues getting the chart to work using the Readme file. After inspecting the chart I saw that there were some typos in the README.md which are fixed in this pullrequest: #29
However, I was still not able to successfully deploy my secret using my values.yaml file. My pod kept giving an authentication error denied: access forbidden.
When diving deeper into this issue I noticed that the structure of my secrets in different clusters was somewhat different when running: kubectl get secret regcred --output="jsonpath={.data.\.dockerconfigjson}" | base64 --decode
output of secret generated with this command: kubectl create secret docker-registry regcred --docker-server=registry.gitlab.com --docker-username=k8s --docker-password=<token>
As you can see there is an extra auths wrapper. I changed the imagepullsecrets.yaml file to also wrap the object with "auths". This fixed the secret issue. I'm on kubernetes 1.16.6.
What are your thoughts on this?
The text was updated successfully, but these errors were encountered:
Sorry for not responding sooner, I was having health problems.
You are absolutely correct, the current chart's output is indeed incorrect.
Could you please retest using chart version 3.0.0 ( 4362ba7 ) ?
I had some issues getting the chart to work using the Readme file. After inspecting the chart I saw that there were some typos in the README.md which are fixed in this pullrequest: #29
However, I was still not able to successfully deploy my secret using my
values.yaml
file. My pod kept giving an authentication errordenied: access forbidden
.When diving deeper into this issue I noticed that the structure of my secrets in different clusters was somewhat different when running:
kubectl get secret regcred --output="jsonpath={.data.\.dockerconfigjson}" | base64 --decode
output of secret created by this chart
output of secret generated with this command:
kubectl create secret docker-registry regcred --docker-server=registry.gitlab.com --docker-username=k8s --docker-password=<token>
As you can see there is an extra
auths
wrapper. I changed theimagepullsecrets.yaml
file to also wrap the object with"auths"
. This fixed the secret issue. I'm on kubernetes1.16.6
.What are your thoughts on this?
The text was updated successfully, but these errors were encountered: