You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have seen that the shoot list on production clusters sometimes does not show any clusters. The list appears empty, even though they can be fetched directly from the kube apiserver e.g. using kubectl.
Restarting the dashboard pod solves the problem temporarily.
We have seen that this issue starts to occur with mass disconnections of websockets, e.g. when the nginx ingress controller detects a configuration change and restarts it's backends.
I could reproduce the issue locally and websockets/ws#1617 (comment) is a pretty good description of what I saw in the debugger. The issue seems to be solved with ws 7.1.2.
There is already a PR on engine.io to upgrade to ws 7.1.2
The text was updated successfully, but these errors were encountered:
The fix is part of engine.io 3.4.0.
But the socket.io release contains engine.io 3.3.1 -> so no, unfortunately not yet within the latest socket.io release
We have seen that the shoot list on production clusters sometimes does not show any clusters. The list appears empty, even though they can be fetched directly from the kube apiserver e.g. using kubectl.
Restarting the dashboard pod solves the problem temporarily.
We have seen that this issue starts to occur with mass disconnections of websockets, e.g. when the nginx ingress controller detects a configuration change and restarts it's backends.
I could reproduce the issue locally and websockets/ws#1617 (comment) is a pretty good description of what I saw in the debugger. The issue seems to be solved with
ws
7.1.2.There is already a PR on
engine.io
to upgrade tows
7.1.2The text was updated successfully, but these errors were encountered: