[ws-manager-bridge] Garbage-collect workspace instances whose workspace clusters are not available anymore

[geropl]

context:

• internal slack discussion: https://gitpod.slack.com/archives/C020VCB0U5A/p1636974437234400?thread_ts=1636963076.228900&cid=C020VCB0U5A
• PR: [ws-manager-bridge] Support forced cluster dereg #6682

Front conversations

[JanKoehnlein]

I am trying to reverse-engineer the action for this issue form the given context. Please clarify: Is this about

1. adding an additional (timeout-based?) mechanism on the ws-manager-bridge that also works when the cluster goes donw without deregistering, or
2. taking further action in the ws-manager-bridge when receiving a forced deregistration request
3. None of the above (please specify)

[geropl]

Sorry for lagging details: This is about adding a mechanism that ensures we don't leak workspaces dangling in any state other than stopped once a workspace cluster is de-registered.

We could discuss whether this should be:
a) timeout-based, and workspace may re-appear if we re-register a workspace quickly enough. This would make it a bit more fault-tolerant and safe. This is samewhat tricky, as we need to poll d_b_workspace by region. But it's impossible atm for ws-manager-bridge to distinguish between "I'm don't know this region but someone else does" and "no-one is governing this region".
b) using the "forced de-registration" request as signal might serve as a first version. Although this might lead to unwanted fall-out in case we mis-used the gptcl clusters command.

a) will become possible once we have the changes required for simplified meta, hence I did not prioritize this, yet.

[geropl]

Assigned this to epic "Simplified Multi-Meta"

[geropl]

Unassigned, because there's no immediate connection

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.