-
Notifications
You must be signed in to change notification settings - Fork 9.4k
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] Configuring the node as master instead as replica when redis on the same k8s node and exposed outside by HostIP #16925
Comments
Thanks for creating this issue and the associated PR. The team will review it and provide feedback. Once merged the PR, this issue will be automatically closed. |
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. |
Reopen |
Name and Version
bitnami/redis 17.11.3
What architecture are you using?
amd64
What steps will reproduce the bug?
install helm chart with custom parameters
Are you using any custom parameters or values?
What is the expected behavior?
What do you see instead?
instead of:
use:
I'll do a PR
Additional information
When installing chart with custom parameters above and not setting hard affinity rules, redis nodes than launch at the same k8s node as a master will be configuring as master, because equal values [[ "$REDIS_MASTER_HOST" == "$(get_full_hostname "$HOSTNAME")" ]]
The text was updated successfully, but these errors were encountered: