fix: retain application volumes and protect database rollouts - #21
Merged
Merged
Conversation
|
Navigate logical layers of code changes, visualize relationships, and explore their blast radius. Note Currently processing new changes in this PR. This may take a few minutes, please wait... ⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Advanced Run ID: 📒 Files selected for processing (8)
✨ Finishing Touches📝 Generate docstrings
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
This was referenced Sep 17, 2026
toto04
approved these changes
Sep 30, 2026
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
2 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.
Protect all seven managed Longhorn PVCs from Argo pruning and application deletion with
Prune=false,Delete=false. Use Recreate for the single PostgreSQL instance so a rollout cannot start competing writers on its volume, and add pg_isready readiness without a liveness restart loop. Give the bot 90 seconds for graceful shutdown.Validation: both manifest regression scripts pass, including retention and PostgreSQL rollout checks. Every changed manifest passed
kubectl apply --dry-run=serveragainst the current cluster. No manifests were applied by these checks.Rollout: the PostgreSQL pod-template change causes a graceful database recreation and brief downtime; schedule the sync accordingly. The bot grace-period change also recreates its pod: confirm its Redis connection and fallback-buffer flush before sync. PVCs and data remain in place. Existing PVs were separately changed to Retain during the incident; PVC annotations complement that protection. There are no image or node-count changes in this PR.
Related incident PRs: backend, telegram, terraform.