Chance Zibolski

> What's more efficient would depend on how many namespaces there are, and what proportion of them that this Prometheus is interested in. I'd expect specifying a namespace to always...

PR is currently based on https://github.com/cilium/cilium/pull/21181

/test

/test

/test

/test-1.16-4.9

I'll see if this requires any additional work inside the hubble metrics sub-system, but I suspect this may be possible using metrics relabeling or by joining against metrics with kube-state-metrics....

So I was doing some more testing, and it does seem like this is actually not limited to destination IP as I thought. And it's actually not consistently broken either...

The reason behind this behavior makes sense, though it breaks the metrics labels like source/destination pod because the pod name is missing, and obviously the IP being "wrong" can be...

I don't know enough about how packets traverse cilium to have any suggestions on solutions, I think that's something @jrajahalme might be able to answer better.