gh/workflows: Disable BPF masq in ci-datapath

[brb]

It seems to be broken in the direct routing mode. Disable for now in all configurations.

Successful run - https://github.com/cilium/cilium/actions/runs/3952387001/jobs/6767397972.

[julianwiedmann]

For the record, this is meant to fix the following fallout in the bpf-next test:

📋 Test Report
❌ 5/31 tests failed (12/237 actions), 0 tests skipped, 0 scenarios skipped:
Test [no-policies]:
connectivity test failed: 5 tests failed
❌ no-policies/pod-to-world/http-to-one.one.one.one-0: cilium-test/client-755fb678bd-r9qf5 (10.244.1.124) -> one.one.one.one-http (one.one.one.one:80)
❌ no-policies/pod-to-world/https-to-one.one.one.one-0: cilium-test/client-755fb678bd-r9qf5 (10.244.1.124) -> one.one.one.one-https (one.one.one.one:443)
❌ no-policies/pod-to-world/https-to-one.one.one.one-index-0: cilium-test/client-755fb678bd-r9qf5 (10.244.1.124) -> one.one.one.one-https-index (one.one.one.one:443)
❌ no-policies/pod-to-world/http-to-one.one.one.one-1: cilium-test/client2-5b97d7bc66-dm6bd (10.244.1.206) -> one.one.one.one-http (one.one.one.one:80)
❌ no-policies/pod-to-world/https-to-one.one.one.one-1: cilium-test/client2-5b97d7bc66-dm6bd (10.244.1.206) -> one.one.one.one-https (one.one.one.one:443)
❌ no-policies/pod-to-world/https-to-one.one.one.one-index-1: cilium-test/client2-5b97d7bc66-dm6bd (10.244.1.206) -> one.one.one.one-https-index (one.one.one.one:443)
Test [to-entities-world]:
❌ to-entities-world/pod-to-world/http-to-one.one.one.one-0: cilium-test/client-755fb678bd-r9qf5 (10.244.1.124) -> one.one.one.one-http (one.one.one.one:80)
❌ to-entities-world/pod-to-world/http-to-one.one.one.one-1: cilium-test/client2-5b97d7bc66-dm6bd (10.244.1.206) -> one.one.one.one-http (one.one.one.one:80)
Test [client-egress-l7]:
❌ client-egress-l7/pod-to-world/http-to-one.one.one.one-1: cilium-test/client2-5b97d7bc66-dm6bd (10.244.1.206) -> one.one.one.one-http (one.one.one.one:80)
Test [client-egress-l7-named-port]:
❌ client-egress-l7-named-port/pod-to-world/http-to-one.one.one.one-1: cilium-test/client2-5b97d7bc66-dm6bd (10.244.1.206) -> one.one.one.one-http (one.one.one.one:80)
Test [to-fqdns]:
❌ to-fqdns/pod-to-world/http-to-one.one.one.one-0: cilium-test/client-755fb678bd-r9qf5 (10.244.1.124) -> one.one.one.one-http (one.one.one.one:80)
❌ to-fqdns/pod-to-world/http-to-one.one.one.one-1: cilium-test/client2-5b97d7bc66-dm6bd (10.244.1.206) -> one.one.one.one-http (one.one.one.one:80)
Error: Process completed with exit code 1.

[squeed]

/test
(edit: sorry, wrong PR)

[squeed]

Is there a release-blocking issue to track re-enabling this test? Why is it broken?

[brb]

Is there a release-blocking issue to track re-enabling this test? Why is it broken?

@squeed I'm currently investigating this. Could be just matter of the KIND configuration, and I will keep posted. Anyway, this should not prevent this PR from being merged.

[pchaigno]

Do we need an issue to track this and eventually reenable it?

[brb]

Do we need an issue to track this and eventually reenable it?

👍 If I don't fix it by EOD, then I will create an issue.

[brb]

#23283 🤔