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
htpasswdString is broken on its own #1210
Comments
@Vad1mo thanks for the bug filing. Do you happen to have spare time to submit a PR for this? |
Let's update the doc to declare that it's users' responsibility to make sure the |
…d Sufliarsky <richard.sufliarsky@gmail.com>
Signed-off-by: Richard Sufliarsky <richard.sufliarsky@gmail.com>
Signed-off-by: Richard Sufliarsky <richard.sufliarsky@gmail.com>
This issue is being marked stale due to a period of inactivity. If this issue is still relevant, please comment or remove the stale label. Otherwise, this issue will close in 30 days. |
@Vad1mo any work around for the helm chart version for simple case of docker login to work? |
The only solution that is working is to set registry.credentials.password together with registry.credentials.htpasswdString |
@Vad1mo helm set externalURL is also working for me. Many thanks. |
registry.credentials.htpasswdString
Is supposed to be an alternative to username and password:
However, the implementation of
htpasswdString
in the Helm Chart is broken, so if you sethtpasswdString
you can't login. Core and Job are using different passwords:This search result summarizes why it is not working https://github.com/goharbor/harbor-helm/search?q=registry.credentials.password
Summary why htpasswdString is not working:
REGISTRY_CREDENTIAL_PASSWORD: {{ .Values.registry.credentials.password | b64enc | quote }}
REGISTRY_CREDENTIAL_PASSWORD: {{ .Values.registry.credentials.password | b64enc | quote }}
Both Jobservice and Core are still trying to use
registry.credentials.password
which is different.The only solution that is working is to set
registry.credentials.password
together withregistry.credentials.htpasswdString
But in that case the Documentation needs an update.
The text was updated successfully, but these errors were encountered: