Documentation for pod scaling and disruption budgets #106
Conversation
This file contains 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
ahockersten
force-pushed
the
add-some-docs-for-pod-scaling-etc
branch
from
4a5597f
to
2ff636e
Compare
ahockersten
changed the title
This partially resolves #90.
ahockersten
force-pushed
the
add-some-docs-for-pod-scaling-etc
branch
from
2ff636e
to
17d0fba
Compare
NissesSenap
reviewed
Mar 1, 2022
| that node is destroyed, your application experiences downtime. You will also not have any protection against the applications running in different zones, which could also cause issues if a zone suddenly | ||
| goes down. | ||
|
|
||
| We recommend adding the following configuration under `spec` for each of your deployments. |
There was a problem hiding this comment.
You are talking about antiaffinity. This section was probably prepared for PDB.
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.
This adds documentation about pod scaling and disruption budgets, together with our recommendations. This touches on #90, but I don't think it resolves it fully.