-
Notifications
You must be signed in to change notification settings - Fork 2.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CI: Change cloud regions #30378
Merged
Merged
CI: Change cloud regions #30378
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
maintainer-s-little-helper
bot
added
the
dont-merge/needs-release-note-label
The author needs to describe the release impact of these changes.
label
Jan 23, 2024
brlbil
force-pushed
the
pr/brlbil/change-ci-regions
branch
from
January 23, 2024 12:48
52ff552
to
5527603
Compare
brlbil
added
area/CI
Continuous Integration testing issue or flake
area/CI-improvement
Topic or proposal to improve the Continuous Integration workflow
labels
Jan 23, 2024
/ci-aks |
/ci-awscni |
/ci-eks |
/ci-external-workloads |
/ci-gke |
/ci-aks |
/ci-awscni |
/ci-eks |
/ci-external-workloads |
/ci-gke |
/ci-aks |
/ci-awscni |
/ci-eks |
/ci-external-workloads |
/ci-gke |
brlbil
force-pushed
the
pr/brlbil/change-ci-regions
branch
from
January 26, 2024 12:32
5527603
to
e1d3299
Compare
/ci-awscni |
/ci-aks |
/ci-gke |
/ci-eks |
/ci-external-workloads |
/ci-aks |
/ci-gke |
brlbil
force-pushed
the
pr/brlbil/change-ci-regions
branch
from
January 27, 2024 05:44
e1d3299
to
34ef603
Compare
/ci-aks |
/ci-gke |
maintainer-s-little-helper
bot
added
the
ready-to-merge
This PR has passed all tests and received consensus from code owners to merge.
label
Feb 1, 2024
nbusseneau
added
backport-pending/1.13
The backport for Cilium 1.13.x for this PR is in progress.
and removed
needs-backport/1.13
This PR / issue needs backporting to the v1.13 branch
labels
Feb 8, 2024
maintainer-s-little-helper
bot
moved this from Needs backport from main
to Backport pending to v1.13
in 1.13.12
Feb 8, 2024
nbusseneau
added
backport-pending/1.14
The backport for Cilium 1.14.x for this PR is in progress.
and removed
needs-backport/1.14
This PR / issue needs backporting to the v1.14 branch
labels
Feb 8, 2024
maintainer-s-little-helper
bot
moved this from Needs backport from main
to Backport pending to v1.14
in 1.14.7
Feb 8, 2024
12 tasks
nbusseneau
added
backport-pending/1.15
The backport for Cilium 1.15.x for this PR is in progress.
and removed
needs-backport/1.15
This PR / issue needs backporting to the v1.15 branch
labels
Feb 8, 2024
github-actions
bot
added
backport-done/1.15
The backport for Cilium 1.15.x for this PR is done.
backport-done/1.14
The backport for Cilium 1.14.x for this PR is done.
and removed
backport-pending/1.15
The backport for Cilium 1.15.x for this PR is in progress.
backport-pending/1.14
The backport for Cilium 1.14.x for this PR is in progress.
labels
Feb 9, 2024
github-actions
bot
added
backport-done/1.13
The backport for Cilium 1.13.x for this PR is done.
and removed
backport-pending/1.13
The backport for Cilium 1.13.x for this PR is in progress.
labels
Feb 9, 2024
This was referenced Feb 13, 2024
michi-covalent
moved this from Needs backport from main
to Backport done to v1.15
in 1.15.1
Feb 14, 2024
This was referenced Apr 3, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
area/CI
Continuous Integration testing issue or flake
area/CI-improvement
Topic or proposal to improve the Continuous Integration workflow
backport-done/1.13
The backport for Cilium 1.13.x for this PR is done.
backport-done/1.14
The backport for Cilium 1.14.x for this PR is done.
backport-done/1.15
The backport for Cilium 1.15.x for this PR is done.
ready-to-merge
This PR has passed all tests and received consensus from code owners to merge.
release-note/ci
This PR makes changes to the CI.
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.
Scheduled workflows run all the supported k8s versions on different regions. During some flake investigation, I have realized that regions in or close to the US take less time than others. Due to long-running tests, some workflows fail.
This PR changes regions to ones in the US or Canada. Run times before and after are down below.
Scheduled tests are simulated and links to the successful runs are below.
aks
aws-cni
eks
external-workloads
gke
Note: GKE runs 4 tests per k8s version, they all have similar run times, for simplicity only one of them was included.
As a side effect, Fixes: #30312
Average run times before the change
Average run times after the change