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
Because of Ingress implementation details in k8s infra we have a situation when websocket connection from workspace-loader to master gets closed.
Since workspace-loader is using such a connection it gets stuck when this happens and doesn't open IDE when workspace becomes running.
UD handle this situation with automatic reconnection of a websocket. We need the same functionality in workspace-loader.
This leads to a broken workspace start on kubernetes infrastructure.
Reproduction Steps
OS and version:
Diagnostics:
The text was updated successfully, but these errors were encountered:
akurinnoy
added
status/in-progress
This issue has been taken by an engineer and is under active development.
and removed
status/open-for-dev
An issue has had its specification reviewed and confirmed. Waiting for an engineer to take it.
labels
Jul 20, 2018
Description
Because of Ingress implementation details in k8s infra we have a situation when websocket connection from workspace-loader to master gets closed.
Since workspace-loader is using such a connection it gets stuck when this happens and doesn't open IDE when workspace becomes running.
UD handle this situation with automatic reconnection of a websocket. We need the same functionality in workspace-loader.
This leads to a broken workspace start on kubernetes infrastructure.
Reproduction Steps
OS and version:
Diagnostics:
The text was updated successfully, but these errors were encountered: