Scaleset monitor #31
Draft
Scaleset monitor #31
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
If a scaleset fails, then this will automatically delete the failed scale-set and make a new one. For the future, we could add other features to this monitor, including book-keeping changes that are made, e.g., using the Azure portal.
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.
If a scaleset fails, then this will automatically delete the
failed scale-set and make a new one.
For the future, we could add other features to this monitor, including
book-keeping changes that are made, e.g., using the Azure portal.
@jkwashbourne this is to address the failed scale-sets that you have observed. Please note that I was not able to fully test this because I was not able to reproduce the failed scale-set. So, feel free to try this out, but I'll definitely want to test properly before merging.