You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We've been running into an issue when using SSL with redis where the SSL connection sometimes hangs. In order to mitigate this, I was going to try turning off SSL within our k8s cluster and still leaving SSL for external connections. Not sure if this is the approach (open to suggestions) but when trying to pursue it, it looked like I couldn't configure multiple ports for the redis pod.
What is the feature you are proposing to solve the problem?
The feature would be to allow for multiple ports for redis, allowing SSL and non-SSL ports for redis. Another component of this would be to allow for switching the liveness/readiness probes from SSL-based to use the non-SSL port since that traffic stays within the host.
What alternatives have you considered?
We are currently working to handle other components that may be overloading our redis instance. We're also trying to determine why this one client is now having SSL problems now instead of earlier on their app itself.
The text was updated successfully, but these errors were encountered:
Name and Version
bitnami/redis 20.1.7
What is the problem this feature will solve?
We've been running into an issue when using SSL with redis where the SSL connection sometimes hangs. In order to mitigate this, I was going to try turning off SSL within our k8s cluster and still leaving SSL for external connections. Not sure if this is the approach (open to suggestions) but when trying to pursue it, it looked like I couldn't configure multiple ports for the redis pod.
What is the feature you are proposing to solve the problem?
The feature would be to allow for multiple ports for redis, allowing SSL and non-SSL ports for redis. Another component of this would be to allow for switching the liveness/readiness probes from SSL-based to use the non-SSL port since that traffic stays within the host.
What alternatives have you considered?
We are currently working to handle other components that may be overloading our redis instance. We're also trying to determine why this one client is now having SSL problems now instead of earlier on their app itself.
The text was updated successfully, but these errors were encountered: