ci: add AKS workflow #15466
Merged
ci: add AKS workflow #15466
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
|
Testing via #15468. |
|
I've removed the spot nodepool as it seems to be too unwieldy for connectivity tests at the moment... Not a major concern, just too bad we can't use it. Will make a note to retry it later. |
|
Have some issue where Will troubleshoot on Monday. |
|
Alright so it seems the issue lies with |
This workflow has been migrated from https://github.com/cilium/cilium-cli/ as part of the CI 3.0 initiative, and adapted based on the previous migration made for GKE. See #15416 and #15482 for more details on the structure and adaptations made. Triggers: - `aks.yaml` is triggered automatically when a comment starting with `ci-aks` is made on an PR. In this case, a GitHub status check is manually registered for the PR SHA commit, and will show up in the PR status checks with a link to the workflow run. - `aks.yaml` is also triggered automatically on merge to `master`. In this case a GitHub status check is already automatically registered by the `push` event, so we skip manual status check registering. - A commented `pull_request` trigger is available for workflow developers: it may be uncommented and used in test PRs for testing the workflow using the `ci-run/gke` label (requires write privileges as it will only work for PRs from branches in the Cilium repo, not from fork). Of course it should be left commented for the real PR. Signed-off-by: Nicolas Busseneau <nicolas@isovalent.com>
|
Link to test run for this version of the workflow, from #15468 : https://github.com/cilium/cilium/actions/runs/723298807 |
nebril
approved these changes
Apr 7, 2021
aanm
approved these changes
Apr 7, 2021
nebril
added
the
ready-to-merge
This was referenced Apr 28, 2021
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.
This workflow has been migrated from https://github.com/cilium/cilium-cli/ as part of the CI 3.0 initiative, and adapted based on the previous migration made for GKE.
See #15416 and #15482 for more details on the structure and adaptations made.
Triggers:
aks.yamlis triggered automatically when a comment starting withci-aksis made on an PR. In this case, a GitHub status check is manually registered for the PR SHA commit, and will show up in the PR status checks with a link to the workflow run.aks.yamlis also triggered automatically on merge tomaster. In this case a GitHub status check is already automatically registered by thepushevent, so we skip manual status check registering.pull_requesttrigger is available for workflow developers: it may be uncommented and used in test PRs for testing the workflow using theci-run/gkelabel (requires write privileges as it will only work for PRs from branches in the Cilium repo, not from fork). Of course it should be left commented for the real PR.