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: update cilium-cli to v0.9.2 #17706
Conversation
ci-aks |
ci-eks |
ci-awscni |
ci-gke |
ci-external-workloads |
All affected GH action workflows passed:
Removing test commit. |
530c275
to
23dad88
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good, except for one change that looks unrelated.
@@ -37,6 +37,7 @@ addons: | |||
packages: | |||
- kernel-package | |||
- gnupg | |||
- ipset |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why is this change necessary here?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is unrelated and I forgot to revert before creating the commit. Will drop that change.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Turns out I forgot to push the actual change doing this 🤦 sorry about that!
I can send a PR removing it again if needed. This was meant to silence some log warning related to missing ipset
binary during privileged tests on Travis CI.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've had to rebase #17687 which also changes .travis.yaml
, so I've added a commit to that PR to drop ipset
again.
23dad88
to
84b6275
Compare
@@ -266,11 +266,6 @@ jobs: | |||
cilium hubble enable --context ${{ steps.contexts.outputs.context1 }} ${{ steps.vars.outputs.hubble_enable_defaults }} | |||
cilium hubble enable --context ${{ steps.contexts.outputs.context2 }} ${{ steps.vars.outputs.hubble_enable_defaults }} --relay=false |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This slightly increase the test run, because first cluster hubble will wait for hubble to be ready and only then enable hubble in second cluster (and wait). Would be nice to parallelize this, but this is a nit.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good point. I guess we could run the first one with --wait=false
to circumvent that and keep the cilium status --wait
in this case.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done. Incremental diff:
diff --git a/.github/workflows/conformance-multicluster-v1.10.yaml b/.github/workflows/conformance-multicluster-v1.10.yaml
index db0f4e4fde9d..a0ff7ab91c8e 100644
--- a/.github/workflows/conformance-multicluster-v1.10.yaml
+++ b/.github/workflows/conformance-multicluster-v1.10.yaml
@@ -260,8 +260,9 @@ jobs:
- name: Enable Relay
run: |
- cilium hubble enable --context ${{ steps.contexts.outputs.context1 }} ${{ steps.vars.outputs.hubble_enable_defaults }}
+ cilium hubble enable --context ${{ steps.contexts.outputs.context1 }} ${{ steps.vars.outputs.hubble_enable_defaults }} --wait=false
cilium hubble enable --context ${{ steps.contexts.outputs.context2 }} ${{ steps.vars.outputs.hubble_enable_defaults }} --relay=false
+ cilium status --wait --context ${{ steps.contexts.outputs.context1 }}
- name: Enable cluster mesh
run: |
diff --git a/.github/workflows/conformance-multicluster.yaml b/.github/workflows/conformance-multicluster.yaml
index 0b405066c0a1..43384814917a 100644
--- a/.github/workflows/conformance-multicluster.yaml
+++ b/.github/workflows/conformance-multicluster.yaml
@@ -263,8 +263,9 @@ jobs:
- name: Enable Relay
run: |
- cilium hubble enable --context ${{ steps.contexts.outputs.context1 }} ${{ steps.vars.outputs.hubble_enable_defaults }}
+ cilium hubble enable --context ${{ steps.contexts.outputs.context1 }} ${{ steps.vars.outputs.hubble_enable_defaults }} --wait=false
cilium hubble enable --context ${{ steps.contexts.outputs.context2 }} ${{ steps.vars.outputs.hubble_enable_defaults }} --relay=false
+ cilium status --wait --context ${{ steps.contexts.outputs.context1 }}
- name: Enable cluster mesh
run: |
`cilium hubble enable` now correctly waits for Cilium status to be ready. Thus, the extra `cilium status --wait` after enabling Hubble can be avoided. Signed-off-by: Tobias Klauser <tobias@cilium.io>
84b6275
to
a56ce88
Compare
ci-multicluster |
Multicluster test passed after latest changes (see #17706 (review) for context and incremental diff): https://github.com/cilium/cilium/runs/4022972414?check_suite_focus=true. Removing test commit and marking as ready to merge. |
a56ce88
to
4d3764b
Compare
cilium hubble enable
now correctly waits for Cilium status to beready. Thus, the extra
cilium status --wait
after enabling Hubble canbe avoided.