Unexpected supervisor timeout connection in ring0 against ws-daemon

[aledbf]

Bug description

Error:

  Warning  Unhealthy         45m (x21 over 45m)  kubelet  Readiness probe failed: Get "http://10.20.235.101:22999/_supervisor/v1/status/content/wait/true": dial tcp 10.20.235.101:22999: connect: connection refused

❯ k logs ws-xxxxxxxxxxxxxxxxxxxxxxxxx
{"@type":"type.googleapis.com/google.devtools.clouderrorreporting.v1beta1.ReportedErrorEvent","error":"socket did not appear before context was canceled:\n    github.com/gitpod-io/gitpod/workspacekit/cmd.connectToInWorkspaceDaemonService\n        /tmp/build/components-workspacekit--app.f18d0d86f148cde6d618856b569ed0046be5db7c/cmd/rings.go:938","level":"error","message":"cannot connect to daemon","ring":0,"serviceContext":{"service":"workspacekit","version":"commit-65f001db3c95f8c54ea735c4ca676ef751acfb67"},"severity":"ERROR","time":"2022-05-06T14:13:42Z"}
{"level":"info","message":"done","ring":0,"serviceContext":{"service":"workspacekit","version":"commit-65f001db3c95f8c54ea735c4ca676ef751acfb67"},"severity":"INFO","time":"2022-05-06T14:13:42Z"}

Steps to reproduce

Not clear. The side effect of this issue is the workspace stays in Terminating state until the finalizer is removed.

Workspace affected

No response

Expected behavior

No response

Example repository

No response

Anything else?

No response

[kylos101]

@utam0k can we close this issue? I ask because you did #10085.

[utam0k]

@kylos101 yes, we can.