test(e2e): add location option to the e2e pipeline #37
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
tallaxes
approved these changes
Nov 16, 2023
|
Old E2E run, pre-merge: |
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
Wanting to give us more flexibility for manual e2e testing, and/or any additional automated testing by opening up the ability to specify the location for a e2e test to be run in.
How was this change tested?
Here is the branch specific E2E test, which is also targeting
eastus:https://github.com/Azure/karpenter/actions/runs/6895118672/job/18758391880
Note: the failures are within GPU is an expected current quota issue, and PVC is flaky atm. With the overall confirmation of the tests running in the given region and the rest of the check-in tests passing, I'm completing this.
*
Does this change impact docs?
Release Note