Remove Spot instance for PAYG #106
Merged
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
JaydenLiang
reviewed
Jul 20, 2023
There was a problem hiding this comment.
Hi @jvhoof , you have a templates/blah file here. What is it used for?
|
@JaydenLiang That was a temporary clipboard that I should have removed. Removed from the PR now. |
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.
By default, spot instances are enable in the autoscale template for the PAYG VMSS deployment. Spot instances have become more difficult to get a hold of recently and are not optimal for a statefull firewall. They can be evicted at any time resulting in dead connections.
https://azure.microsoft.com/en-us/products/virtual-machines/spot/