[bitnami/redis] Sentinel is not able to promote a replica to a new master about charts HOT 6 CLOSED

What are the values used to deploy the chart?

from charts.

Hi @carrodher,

We were able to resolve this issue, the issue was with the TLS port incorrect configuration due to which the prehook step for the redis and sentinel were not working.

However, can you please answer the below questions/queries that we have:

1. Say suppose, we are performing a helm upgrade and we want this to happen seamlessly without affecting/loosing the existing keys.
2. Is there any scenario that should be taken into consideration when we might loose the keys during the failover or during any situation?

Currently, when I tested with multiple keys and issued the kubectl delete command, one of the replica is getting promoted to the master and the keys are intact. Is there any situation I missed or should be cautious about?

from charts.

The issue may not be directly related to the Bitnami container image or Helm chart, but rather to how the application is being utilized or configured in your specific environment.

If you have any questions about the application itself, customizing its content, or questions about technology and infrastructure usage, we highly recommend that you refer to the forums and user guides provided by the project responsible for the application or technology.

With that said, we'll keep this ticket open until the stale bot automatically closes it, in case someone from the community contributes valuable insights.

from charts.

Thanks a lot @carrodher.
Really appreciate your timely help.

from charts.

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.

from charts.

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.

from charts.