We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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-cluser:7.4
During the bootstrap., why are we updating the redis node IPs in the nodes.conf file instead of issuing redis-cli cluster meet command?
whats the advantage we are gaining over redis-cli cluster meet command?
https://github.com/bitnami/containers/blob/main/bitnami/redis-cluster/7.4/debian-12/rootfs/opt/bitnami/scripts/librediscluster.sh#L205
Use redis-cli cluster meet instead of update IPs.
No response
The text was updated successfully, but these errors were encountered:
Hi,
This was because the command was causing issues in Kubernetes installations, where the IPs are ephemeral and we needed to update them this way.
Sorry, something went wrong.
javsalgar
No branches or pull requests
Name and Version
bitnami/redis-cluser:7.4
What is the problem this feature will solve?
During the bootstrap., why are we updating the redis node IPs in the nodes.conf file instead of issuing redis-cli cluster meet command?
whats the advantage we are gaining over redis-cli cluster meet command?
https://github.com/bitnami/containers/blob/main/bitnami/redis-cluster/7.4/debian-12/rootfs/opt/bitnami/scripts/librediscluster.sh#L205
What is the feature you are proposing to solve the problem?
Use redis-cli cluster meet instead of update IPs.
What alternatives have you considered?
No response
The text was updated successfully, but these errors were encountered: