docs: update CATALOG.md for observability-pod-disruption-budget#3498
Merged
sebrandon1 merged 1 commit intoredhat-best-practices-for-k8s:mainfrom Mar 3, 2026
Merged
Conversation
Regenerate CATALOG.md to reflect the zone-aware PDB validation changes introduced in PR redhat-best-practices-for-k8s#3467. The observability-pod-disruption-budget test case now documents the zone-aware checks that ensure workloads can survive an entire zone going offline during platform upgrades. Signed-off-by: Gonzalo Reyero Ferreras <greyerof@redhat.com>
Collaborator
|
from change #3498: |
sebrandon1
approved these changes
Mar 3, 2026
sebrandon1
merged commit b8be291
into
redhat-best-practices-for-k8s:main
15 checks passed
Collaborator
|
from change #3498: |
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
3 participants
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.
Regenerate CATALOG.md to reflect the zone-aware PDB validation changes introduced in PR #3467. The observability-pod-disruption-budget test case now documents the zone-aware checks that ensure workloads can survive an entire zone going offline during platform upgrades.