/test

I went back and forth a bit on the release note for this. In general PRs should have only one release note label and since this is fixing a regression in v1.17.0-pre.3 I figure that release-note/bug is probably the most appropriate.

Could you also update the flag declaration back to StringSlice in daemon/cmd/daemon_main.go?

Oh, thank you very much! Done.

/test

Additionally marking for backport to v1.15, as #36103 got marked as well.

I agree that if we are backporting #36103 then this should also be backported. I don't understand why we are nominating #36103 however because it's outside the regular backport criteria: https://docs.cilium.io/en/stable/contributing/release/backports/#backport-criteria . CC @nbusseneau Users should be upgrading to the latest stable release if they want all the latest bugfixes. We really should be only backporting critical changes or security fixes to the older releases at this stage, as every change comes with a degree of risk that we break something else in the older releases. The less churn we have on older branches, the less burden we take on as an open source community due to the work of backporting and potentially then also subsequently fixing broken backports on older releases. This translates into more time we can spend making the current stable or next feature release better.