Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

imagepullsecrets chart issue #30

Open
stijlbreuk-dev opened this issue May 8, 2020 · 2 comments
Open

imagepullsecrets chart issue #30

stijlbreuk-dev opened this issue May 8, 2020 · 2 comments

Comments

@stijlbreuk-dev
Copy link

stijlbreuk-dev commented May 8, 2020

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 created by this chart

{"registry.gitlab.com":{"auth":"[REDACTED]","password":"[REDACTED]","username":"[REDACTED"}}%                                                                                                                

output of secret generated with this command:
kubectl create secret docker-registry regcred --docker-server=registry.gitlab.com --docker-username=k8s --docker-password=<token>

{"auths":{"registry.gitlab.com":{"auth"[REDACTED]", "password":[REDACTED]","username":"[REDACTED"}}}%               

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?

gabibbo97 added a commit that referenced this issue May 28, 2020
@gabibbo97
Copy link
Owner

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 ) ?

@stijlbreuk-dev
Copy link
Author

No worries 😊 This seems to work! Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants