Limiting user disruption when unexpected events occur
The first challenge that the Isolation working group will address is how to limit disruption to our users when there are problems on GitLab.com.
These problems may arise from accidental noisy neighbours, abusive users, or even planned upgrades that are not progressing as expected. When these events occur, we want to shield our users as far as possible from the piece of the system that is failing.
This issue is driven by us and our SLO. We do not want to have any customer actions, whether intentional or not, negatively impact the experience or our other customers. The related issue #34010 is driven by the customer. They want assurances, for whatever reason, that their data, services and resources are isolated from other customers.