-
Notifications
You must be signed in to change notification settings - Fork 740
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
Cannot use existingSecret for external redis #1735
Comments
Duplicate of #1641 |
This is not a duplicate because I'm not using |
Sorry, you're right. Can you render the invalid YAML and paste it here? (you should be able with --debug option) |
It doesn't output any yaml. Just the error
|
@CrimsonFez could you please share with us which version of harbor-helm you are using when facing this issue? Thanks |
1.14.1 |
Hi @CrimsonFez ,
|
I currently deploy with the password in my values, so that works. Here are my values:
|
I have the same issue, install redis with the bitnami chart, install with the custom values:
copy secret to harbor namespace, install harbor chart with:
Errors:
Change the redis chart to:
make no other changes, and Harbor starts working straight away: I would have expected it to fail since I'm still telling Harbor to provide a password in the Helm chart with existingSecret.
|
When I configure an externalSecret from external redis I have the following errors:
From what I can tell this is actually an issue with b64dec from helm.
In _heplers.tpl on line 161 it grabs the existing secret data and decodes it to use when making the config map.
At one point in my testing I was also able to generate the manifest and everything looked fine, the password was in the url, but it still threw the error.
After I replace the lookup with
print "base64string" | b64dec
it still caused the error. I also dont believe that it was an issue with my password since it works just fine if I doprint "password"
.The text was updated successfully, but these errors were encountered: