feat(HA): adding support to have controller in HA #31
Conversation
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
Codecov Report
@@ Coverage Diff @@
## master #31 +/- ##
=======================================
Coverage 83.33% 83.33%
=======================================
Files 1 1
Lines 72 72
=======================================
Hits 60 60
Misses 12 12Continue to review full report at Codecov.
|
pawanpraka1
changed the title
We can have more than one controller in the system, but only one will be the master and others will be slave. Once master is down, one of the slave will take over via lease mechanism and start provisioning/deprovisioning the volumes. Signed-off-by: Pawan <[email protected]>
pawanpraka1
force-pushed
the
lease
branch
3 times, most recently
from
5445cc5 to
2d275f4
Compare
so that no two pods get scheduled on the same node. Also keeping the default replica to 1, if HA feature is required, we can change replica count to 2(or more). Signed-off-by: Pawan <[email protected]>
pawanpraka1
changed the title
kmova
approved these changes
Jan 6, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
We can have more than one controller in the system, but only one will
be the master and others will be slave. Once master is down, one of the slave will
take over via lease mechanism and start provisioning/deprovisioning the volumes.
controller pod will have anti-affinity so that no two pods get scheduled on the same node. Also keeping the default replica to 1, if HA feature is required, we can change replica count to 2(or more).
Signed-off-by: Pawan [email protected]