Marco Iorio

Thanks @sayboras! Could you please apply this patch on top of the config tests to make them more idiomatic? ```diff diff --git a/pkg/clustermesh/common/config_test.go b/pkg/clustermesh/common/config_test.go index 8a4408acdb1b..e3886e67373b 100644 --- a/pkg/clustermesh/common/config_test.go +++...

Thanks again! Here it is the patch for the services part: ```diff diff --git a/pkg/clustermesh/services_test.go b/pkg/clustermesh/services_test.go index 8ae2856c7ea6..73eeb0e20087 100644 --- a/pkg/clustermesh/services_test.go +++ b/pkg/clustermesh/services_test.go @@ -12,6 +12,7 @@ import ( "time"...

> > The Conformance Cluster Mesh failure is legitimate, and is addressed by #32367 (which also bumps the Cilium CLI version). We should wait for that PR to land before...

Hit on https://github.com/cilium/cilium/pull/32436 as well Link: https://github.com/cilium/cilium/actions/runs/9020020285/job/24784243984

Hit on https://github.com/cilium/cilium/pull/32471: https://github.com/cilium/cilium/actions/runs/9035428845/job/24830197194

Hmm, hit again even with the 10 minutes timeout: https://github.com/cilium/cilium/actions/runs/9188138331/job/25267307890 > Errors: cilium cilium-cbkl2 controller cilium-health-ep is failing since 22s (31x): Get "http://10.244.2.6:4240/hello": dial tcp 10.244.2.6:4240: connect: no route to...

> Ok, then my next question is we could get this disaggregated information from ServiceExport + the actual exported service. Then why do we need to introduce this new annotation?...

/test-backport-1.13

/test-backport-1.13

/test-backport-1.13