test(e2e): switch to westus3 for e2e #440
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
Pull Request Test Coverage Report for Build 9964502625Details
💛 - Coveralls |
tallaxes
approved these changes
Jul 16, 2024
Bryce-Soghigian
pushed a commit
that referenced
this pull request
Sep 12, 2024
Co-authored-by: Charlie McBride <[email protected]>
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.
Fixes #
Description
We've been experiencing some allocation issues within the current testing regions.
Did some testing to find a new region, which
westus3seems to be rather well suited for our needs, so switching the testing pipeline there.How was this change tested?
Ran the E2E pipeline for
westus3:https://github.com/Azure/karpenter-provider-azure/actions/runs/9964029669/job/27531436071
While not all successful, did a sanity check within the subscription on quota, and public doc support for multi-zone region, and this appears to be a good region change:
https://learn.microsoft.com/en-us/azure/reliability/availability-zones-service-support
*
Does this change impact docs?
Release Note