-
Notifications
You must be signed in to change notification settings - Fork 8.9k
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
[bitnami/redis-cluster] cannot use tls #14673
Comments
Hello @deveshk0, As you mention in the issue itself: "Since certificate is generated before, we cannot add POD_IP to the certificate, I guess we should mongodb approach and generate certificates as part of init container", have you tried to solve it with that approach? |
I am looking into integrating this - redis/redis#9530 |
This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback. |
Added - bitnami/containers#26832 |
This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback. |
Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary. |
Name and Version
bitnami/redis-cluster all versions
What steps will reproduce the bug?
Client throws error - ERROR (x509: certificate is valid for 127.0.0.1, not 10.233.79.29)
Client is expecting POD_IP to be part of the certificate as it is offered by redis cluster.
Since certificate is generated before, we cannot add POD_IP to teh certificate, I guess we should mongodb approach and generate certificates as part of init container
Are you using any custom parameters or values?
What is the expected behavior?
TLS Communication should worl
What do you see instead?
ERROR (x509: certificate is valid for 127.0.0.1, not 10.233.79.29)
Additional information
No response
The text was updated successfully, but these errors were encountered: