mbhatia

@glibsm I was able to reproduce without hubble relay by directly `kubectl exec` into a cilium pod and running `hubble observe.` top-left: `k exec` into cilium pod; hubble observe not...

@gandro thank you for taking the time to respond. While your explanation regarding L7 traffic makes sense, I also cannot see any L3 traffic related to a service. e.g. I...

In my case, the output is the following: ``` $ k exec -it cilium-zzdg8 -n kube-system -- cilium status | grep KubeProxyReplacement KubeProxyReplacement: Partial [eth0 (DR)] [NodePort (SNAT, 30000-32767, XDP:...

@gandro here is the information you requested. 1) The last element of `cilium service list` matches the service ip of `server-error/liveness-http` ``` $ k exec -it -n kube-system cilium-hjftq --...

@glibsm This is why I am confused because as you can see in the flows, the L7 query is using the service DNS name, yet "destination" resolves to pod IP....