Tam Mach

/test Job 'Cilium-PR-K8s-1.16-kernel-4.9' failed: Click to show. ### Test Name ```test-name K8sDatapathConfig Host firewall With native routing ``` ### Failure Output ```failure-output FAIL: Failed to reach 10.0.1.241:80 from testclient-host-6gwmc ```...

:wave: we will need one review from datapath team cc @cilium/sig-datapath

Thanks for reporting, feel free to shout out if you need any help on submitting fix.

/test Job 'Cilium-PR-K8s-1.25-kernel-net-next' failed: Click to show. ### Test Name ```test-name K8sDatapathConfig Check BPF masquerading with ip-masq-agent DirectRouting ``` ### Failure Output ```failure-output FAIL: Failed to add ip route ```...

/test Job 'Cilium-PR-K8s-1.23-kernel-5.4' failed: Click to show. ### Test Name ```test-name K8sDatapathConfig Host firewall With VXLAN ``` ### Failure Output ```failure-output FAIL: Failed to reach 192.168.56.11:80 from testclient-l9hlq ``` If...

/test

CI failures seem related ``` Error: /home/runner/work/cilium/cilium/src/github.com/cilium/cilium/pkg/datapath/linux/node_linux_test.go:108:41: too many arguments in call to tunnel.NewTunnelMap have (string) want () ```

Removed myself from the review list, as we already have expertise from other reviewers, and I am unfamiliar with this code path.

The loadbalancer name (e.g. internal-a98d614cfbaae4b68a9ff14be5dee82e-107606502.eu-central-1.elb.amazonaws.com) seems to be internal, and might be only resolved within private subnets only. Just want to confirm if you are running cilium CLI in the...

:wave: Thanks for your issue, it's interesting proposal I can say. I didn't use bazel much apart from just direct user. Let me do some research before I can comment....