forked from spotahome/redis-operator
-
Notifications
You must be signed in to change notification settings - Fork 0
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
Add Redis Slave Endpoint to HAProxy Service configuration #35
Closed
Closed
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Might be worth noting that the redis-operator already exposes Services to get at the "master" node, or "slave" nodes of a RedisFailover. I'm not sure I fully understand the cost/benefit equation of doing the same thing with more moving parts via HAProxy.
That said,
BootstrapNode.Port
isI'm confused, so maybe I'm reading this code wrong. Wouldn't this expose the slave nodes of the Replicating RedisFailover on the Port that the "target"/source Redis instance is exposed on?
IF I've understood this correctly, had you considered the following alternatives that avoid overloading the meaning of the Bootstrap.Port:
Footnotes
(https://github.com/powerhome/redis-operator/blob/bd12c9ae881b5b50f34fbb511237b08c35348234/operator/redisfailover/service/generator.go#L451) ↩
(https://github.com/powerhome/redis-operator/blob/632aa3da88ee2a28ccb9fc4f571ddcb556dbd713/operator/redisfailover/service/constants.go#L5) ↩