[v1.11] helm chart: v1.11 base : hubble-ui deployment : restore nodeSelector and tolerations

[BryanStenson-okta]

Fixes: #25181

helm chart: restore setting nodeSelector and tolerations on hubble-ui deployment via `values.yaml`

[maintainer-s-little-helper]

Commit 388d736fa6c72c9263bd190ad570409f52f2b841 does not contain "Signed-off-by".

Please follow instructions provided in https://docs.cilium.io/en/stable/contributing/development/contributing_guide/#developer-s-certificate-of-origin

[joestringer]

/test

[joestringer]

It looks like the test runs are not picking up the correct jobs, as the latest version is not rebased against the latest version of main. You may need to do a git fetch origin and/or git pull --rebase in order to resolve this.

[BryanStenson-okta]

rebase on main, or v1.11? i think i'm confused on the release process for what would be a v1.11.17 release.

i had rebased on the HEAD from v1.11 branch. maybe that's not what i should have done here.

[gandro]

I think the tests are failing because we ran the wrong trigger. /test is supposed to run against main, but this is a backport PR targeting v1.11.

[gandro]

/test-backport-1.11

Job 'Cilium-PR-K8s-1.19-kernel-4.9' failed:

Click to show.

Test Name

K8sServicesTest Checks E/W loadbalancing (ClusterIP, NodePort from inside cluster, etc) Checks service on same node

Failure Output

FAIL: Found 2 k8s-app=cilium logs matching list of errors that must be investigated:

Jenkins URL: https://jenkins.cilium.io/job/Cilium-PR-K8s-1.19-kernel-4.9/2852/

If it is a flake and a GitHub issue doesn't already exist to track it, comment /mlh new-flake Cilium-PR-K8s-1.19-kernel-4.9 so I can create one.

Then please upload the Jenkins artifacts to that issue.

Job 'Cilium-PR-K8s-1.21-kernel-4.9' has 1 failure but they might be new flake since it also hit 1 known flake: #22555 (94.08% similarity)

Job 'Cilium-PR-K8s-1.17-kernel-4.9' hit: #22555 (92.92% similarity)

[jrajahalme]

Failing 4.9 tests are due to known flakes:

• CI: K8sPolicyTest Multi-node policy test with L7 policy using connectivity-check to check datapath: provided port is already allocated #13071
• CI: [v1.11] Jenkins tests failing on 4.9, agent trying to pass BPF ISA set v3 to init.sh #24394

[jrajahalme]

/ci-l4lb-1.11

[jrajahalme]

/test-backport-1.11

Job 'Cilium-PR-K8s-1.22-kernel-4.19' failed:

Click to show.

Test Name

K8sDatapathConfig Host firewall With VXLAN

Failure Output

FAIL: Failed to reach 192.168.56.11:80 from testclient-7sphr

Jenkins URL: https://jenkins.cilium.io/job/Cilium-PR-K8s-1.22-kernel-4.19/1677/

If it is a flake and a GitHub issue doesn't already exist to track it, comment /mlh new-flake Cilium-PR-K8s-1.22-kernel-4.19 so I can create one.

Then please upload the Jenkins artifacts to that issue.

Job 'Cilium-PR-K8s-1.21-kernel-4.9' failed:

Click to show.

Test Name

K8sKafkaPolicyTest Kafka Policy Tests KafkaPolicies

Failure Output

FAIL: Found 2 k8s-app=cilium logs matching list of errors that must be investigated:

Jenkins URL: https://jenkins.cilium.io/job/Cilium-PR-K8s-1.21-kernel-4.9/2636/

If it is a flake and a GitHub issue doesn't already exist to track it, comment /mlh new-flake Cilium-PR-K8s-1.21-kernel-4.9 so I can create one.

Then please upload the Jenkins artifacts to that issue.

[jrajahalme]

test-1.22-4.19 hit known flake #16122,
test-1.21-4.9 hit known flake #24394

[jrajahalme]

/ci-l4lb-1.11

[jrajahalme]

ci-l4lb-1.11 does not trigger