Suspend AZRebalance #37
Closed
Conversation
This file contains hidden or 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
|
+1 I'm having an issue may caused by AZRebalance during deployment, I receive: after that, a new instance created by AZRebalance during deployment has deployed with old revision. I hope this patch will fix that 👊 |
Contributor
Author
|
With the latest commits I made the script fail in case the suspension/resume of the AZRebalance process can't be achieved. I also added the relevant permissions needed for this to work to the README. |
Contributor
Author
|
Closing this PR in favour of #43 which has a more general approach. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
This commit adds the ability to suspend the ASG process AZRebalance before putting the instance in StandBy.
This is to cope with (the edge case) scenarios where the amount of subnets and desired instances forces the ASG to rebalance the instances during the deployment.
If the AutoScaling process was suspended beforhand then it's a noop.