We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
In https://2i2c.freshdesk.com/a/tickets/1070 we had an outage caused by used up disk space. One failure mode for this not being addressed is that our documentation only covers what to do on GCP: https://infrastructure.2i2c.org/sre-guide/common-problems-solutions/#no-space-left-on-device-error We should add the equivalent instructions for Azure.
(Note: I don't believe this is required for AWS as I think that auto-expands.)
Related PR: #3323 Which makes me think this is a very similar process to GCP.
No response
The text was updated successfully, but these errors were encountered:
The closest is step 5 and 6 in #1081 (comment)
Sorry, something went wrong.
No branches or pull requests
Context
In https://2i2c.freshdesk.com/a/tickets/1070 we had an outage caused by used up disk space. One failure mode for this not being addressed is that our documentation only covers what to do on GCP: https://infrastructure.2i2c.org/sre-guide/common-problems-solutions/#no-space-left-on-device-error We should add the equivalent instructions for Azure.
(Note: I don't believe this is required for AWS as I think that auto-expands.)
Related PR: #3323 Which makes me think this is a very similar process to GCP.
Proposal
No response
Updates and actions
No response
The text was updated successfully, but these errors were encountered: