Tobias Klauser

Is there anything preventing this PR from going in? There were some issues in the Go stdlib found using these tests (mention above) and it just recently came up again...

> https://pkg.go.dev/golang.org/x/sys/unix#section-documentation says: > > > These calls return err == nil to indicate success; otherwise err represents an operating system error describing the failure and holds a value of...

> GKE failed with likely flake: https://jenkins.cilium.io/job/Cilium-PR-K8s-GKE/9017/ > > ``` > Cilium operator was not able to get into ready state > Expected > : { > s: "timed out...

/test-gke

Approvals are in, namely for backports that needed special attention due to conflicts. All remaining test failures are known flakes (multicluster) or will be followed up on (L4LB). Merged.

v4.9.326 was [released](https://lore.kernel.org/stable/[email protected]/T/#m81a65caa1127f1b85977b98d2d368c46e2e2fe14). ~I've opened https://github.com/cilium/packer-ci-build/pull/345 to bump our 4.9 CI image.~ Quentin's PR https://github.com/cilium/packer-ci-build/pull/346 is the correct one.

Commit 205810f2785ec09f149251ec827a880ff7560e26 added by this PR caused merge conflicts on backport to v1.10 and v1.11 because it relies on changes from #20453. AFAICT, the main reason we want to backport...

/test-1.16-4.9

Kind conformance test looks related to the cilium-cli update which dropped the `base-version` flag: https://github.com/cilium/cilium/runs/7747502208?check_suite_focus=true I think we'd also need to backport the relevant bits of #20234 (commit 135f522644f0953385df2c5b0a24c4cb9ebe3c5e) for...

Approvals are in (namely for backports that needed special attention) and all remaining test failures are known flakes (AKS, GKE) or will be followed up on (L4LB). Merging this PR.