Hubble UI intermittently stops responding until relay/UI pods are restarted

[gmYusuf]

Running on:
AWS EKS multi arc cluster

Hubble UI Version:
v0.13.2

Description:
When I try to forward the hubble-ui service, sometimes the UI does not respond properly. Restarting the hubble-ui and hubble-relay pods temporarily resolves the problem, but it comes back later.

In the UI, I see this message:

Data streams are reconnecting...
Next attempt in 1.0s.

Expected behavior:
Hubble UI should stay responsive without requiring pod restarts.

Error in backend:
1 reflector.go:569] /app/internal/ns_watcher/k8s/k8s_watcher.go:100: failed to list *v1.Namespace: Get "https://172.20.0.1:443/api/v1/namespaces?limit=500&resourceVersion=0": dial tcp 172.20.0.1:443: i/o timeout time="2025-08-20T07:05:44Z" level=error msg="ns watcher failed" channelId=ff349bab81dcfc29 component=APIServer error="failed to list *v1.Namespace: Get "https://172.20.0.1:443/api/v1/namespaces?limit=500&resourceVersion=0\": dial tcp 172.20.0.1:443: i/o timeout" handler=ControlStream

Observed behavior:
• Port-forwarding to hubble-ui works initially.
• After some time, the UI stops responding and shows the reconnecting message above.
• Restarting the hubble-ui and hubble-relay pods resolves the issue temporarily.