images: Bump Hubble CLI to v0.9.0

[gandro]

This bumps the Hubble CLI to the recently released version 0.9.0. Hubble
CLI v0.9.0 has been released to include the Hubble protobuf API changes
present in Cilium v1.11-rc3 and thus is intended to be bundled with the
final Cilium v1.11 release.

Due to the cyclic dependency between Hubble CLI and Cilium, this PR can
only be done after the feature freeze and thus needs to be backported to v1.11.

[gandro]

/test

Job 'Cilium-PR-K8s-1.23-kernel-4.9' failed and has not been observed before, so may be related to your PR:

Click to show.

Test Name

K8sDemosTest Tests Star Wars Demo

Failure Output

FAIL: failed to ensure kubectl version: failed to run kubectl version

If it is a flake, comment /mlh new-flake Cilium-PR-K8s-1.23-kernel-4.9 so I can create a new GitHub issue to track it.

Job 'Cilium-PR-K8s-1.22-kernel-4.19' failed and has not been observed before, so may be related to your PR:

Click to show.

Test Name

K8sServicesTest Checks service across nodes Tests NodePort BPF Tests with secondary NodePort device

Failure Output

FAIL: Request from k8s1 to service http://[fd04::11]:31135 failed

If it is a flake, comment /mlh new-flake Cilium-PR-K8s-1.22-kernel-4.19 so I can create a new GitHub issue to track it.

Job 'Cilium-PR-K8s-1.16-net-next' failed and has not been observed before, so may be related to your PR:

Click to show.

Test Name

K8sDatapathConfig MonitorAggregation Checks that monitor aggregation restricts notifications

Failure Output

FAIL: failed to ensure kubectl version: failed to download kubectl

If it is a flake, comment /mlh new-flake Cilium-PR-K8s-1.16-net-next so I can create a new GitHub issue to track it.

[gandro]

Test triage (will edit this post as more tests finish)

• https://jenkins.cilium.io/job/Cilium-PR-K8s-1.23-kernel-4.9/33/ failed with a new flake (a similar one was also found in test/contrib: Bump CoreDNS version to 1.8.3 #18018) failed to ensure kubectl version: failed to run kubectl version

• https://jenkins.cilium.io/job/Cilium-PR-K8s-1.16-net-next/2098/ also failed with failed to ensure kubectl version: failed to download kubectl

• https://jenkins.cilium.io/job/Cilium-PR-K8s-1.22-kernel-4.19/39 failed with a similar symptom as describe in CI: K8sServicesTest Checks service across nodes Tests NodePort BPF Tests with direct routing Tests with secondary NodePort device: Exitcode: 42 #12690

• ConformanceAKS seems to have an issue with tunnelfront, i.e. kubectl exec times out for all nodes https://github.com/cilium/cilium/runs/4379812393?check_suite_focus=true - looks like an infrastructure issue, but I have not found an issue for this yet.

• Multicluster https://github.com/cilium/cilium/runs/4379811614?check_suite_focus=true also seems to have failed with a new failiure (which should be unrelated to this PR, as the Hubble CLI is not used in CI 3.0 tests, we rely on the Cilium CLI instead)

Test [no-policies]:
  ❌ no-policies/pod-to-pod/curl-1: cilium-test/client2-5998d566b4-88f7s (10.12.0.111) -> cilium-test/echo-other-node-f4d46f75b-2bzqj (10.20.1.83:8080)
  ❌ no-policies/pod-to-pod/curl-3: cilium-test/client-6488dcf5d4-ngwcz (10.12.0.40) -> cilium-test/echo-other-node-f4d46f75b-2bzqj (10.20.1.83:8080)
Test [allow-all]:
  ❌ allow-all/pod-to-service/curl-0: cilium-test/client-6488dcf5d4-ngwcz (10.12.0.40) -> cilium-test/echo-other-node (echo-other-node:8080)
  ❌ allow-all/pod-to-service/curl-2: cilium-test/client2-5998d566b4-88f7s (10.12.0.111) -> cilium-test/echo-other-node (echo-other-node:8080)
Connectivity test failed: 2 tests failed
  ❌ allow-all/pod-to-pod/curl-1: cilium-test/client-6488dcf5d4-ngwcz (10.12.0.40) -> cilium-test/echo-other-node-f4d46f75b-2bzqj (10.20.1.83:8080)
  ❌ allow-all/pod-to-pod/curl-3: cilium-test/client2-5998d566b4-88f7s (10.12.0.111) -> cilium-test/echo-other-node-f4d46f75b-2bzqj (10.20.1.83:8080)

[gandro]

/ci-aks

[gandro]

/ci-multicluster

[gandro]

/test-1.16-netnext

https://jenkins.cilium.io/job/Cilium-PR-K8s-1.16-net-next/2100/

[gandro]

/test-1.22-4.19

[gandro]

/test-1.23-4.9

Job 'Cilium-PR-K8s-1.23-kernel-4.9' failed and has not been observed before, so may be related to your PR:

Click to show.

Test Name

K8sCustomCalls Basic test with byte-counter

Failure Output

FAIL: failed to ensure kubectl version: failed to download kubectl

If it is a flake, comment /mlh new-flake Cilium-PR-K8s-1.23-kernel-4.9 so I can create a new GitHub issue to track it.

Edit: Another kubectl flake. https://jenkins.cilium.io/job/Cilium-PR-K8s-1.23-kernel-4.9/35/

[gandro]

/test-1.23-4.9

[gandro]

/test-1.16-netnext

Job 'Cilium-PR-K8s-1.16-net-next' failed and has not been observed before, so may be related to your PR:

Click to show.

Test Name

K8sDatapathConfig MonitorAggregation Checks that monitor aggregation restricts notifications

Failure Output

FAIL: failed to ensure kubectl version: failed to download kubectl

If it is a flake, comment /mlh new-flake Cilium-PR-K8s-1.16-net-next so I can create a new GitHub issue to track it.

https://jenkins.cilium.io/job/Cilium-PR-K8s-1.16-net-next/2104/

[gandro]

/test-1.16-netnext

Job 'Cilium-PR-K8s-1.16-net-next' failed and has not been observed before, so may be related to your PR:

Click to show.

Test Name

K8sKafkaPolicyTest Kafka Policy Tests KafkaPolicies

Failure Output

FAIL: failed to ensure kubectl version: failed to download kubectl

If it is a flake, comment /mlh new-flake Cilium-PR-K8s-1.16-net-next so I can create a new GitHub issue to track it.

[gandro]

Previous netnext flakes all are #18060 (which has been fixed on master just now)

Therefore marking this ready to merge so there still is a chance this makes it into v1.11.0.