Repository navigation
fix(deploy): the site reserves 128Mi, so its update fits next to the API in the quota - #9
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
After the last deploy the API pod was refused:
exceeded quota: team-quota, requested: requests.memory=256Mi, used: requests.memory=768Mi. While the site updates, two of its pods run side by side, and at 256Mi each they plus the API filled the namespace's 768Mi.What changes
deploy/forge/app.yaml: the site reserves 128Mi instead of 256Mi (its limit stays 512Mi). The API keeps 256Mi. During a site update: 256 + 128 + 128 = 512 of 768.docs/DEPLOY-FORGE.md: a troubleshooting row for a missing API pod after an update, and how to recover.Checked