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
External Redis with TLS enabled is not possible to set #11331
Comments
I'm trying to connect external elasticache redis service, but I'm having the same issue. Is it solved in any version? |
@natitomattis It doesn't seem so, also see issue here: #13223 |
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. |
Still an issue, please do not close. |
Just to give some workaround hints for anyone struggling with this... you can add an stunnel sidecar to get around this Is this issue a duplicate of #13223? |
close by duplicate with 13223. We will track it overthere |
Its not possible to setup external redis with TLS enabled. Thats usually problem when is Harbor deployed in Azure, AWS with external redis server with TLS enabled ( PaaS ).
The text was updated successfully, but these errors were encountered: