Anupam Ghosh

Hubble doesn't log DROP_NO_SERVICE for Service with no pods behind it

1

As per this comment https://github.com/cilium/cilium/issues/31786#issuecomment-2039532044. Hubble should be logging `DROP_NO_SERVICE` if a Service has no backend pods behind it. But I am not seeing it. There is a Service deployed...

requests.get inside gevent.spawn is getting stuck

20

* gevent version: version `24.2.1` . Installed using pip. * Python version: cPython `3.11.4` downloaded from https://github.com/python/cpython/releases/tag/v3.11.4 * Operating System: Debian 11 kernel version `5.10.0-29-amd64` * requests version: `2.32.3` installed...

TCP doesn't terminate gracefully if node is down

9

## What happened? Before a pod terminates we make the pod unready so that new connections doesn't get routed to it. So, only nodes which NAT Service ExternalIP to pod...