Repository navigation
feat(high-command): manage high-command-postgres via Fleet - #13
Merged
Merged
Conversation
Adopt the hand-applied high-command-postgres Cluster and Pooler (helm.takeOwnership); spec mirrors live object so adoption is a no-op apart from max_slot_wal_keep_size=2GB to stop dead slots filling WAL. Co-authored-by: Cursor <cursoragent@cursor.com>
This was referenced Oct 4, 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
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.


Summary
high-command-postgresCloudNativePG Cluster andhigh-command-postgres-poolerPooler (namespacehigh-command, prd-apps) under GitOps. They were applied by hand and only had alast-applied-configurationannotation.fleet.yaml:helm.takeOwnership: true, so the existing objects are adopted instead of conflicting.max_slot_wal_keep_size: 2GB(reload-only, no restart). It caps WAL retained by a lagging or broken replica's slot. A health review found replica-1crash-looping; it has been rebuilt withkubectl cnpg destroy.Safety
Under Helm adoption, any field missing from the manifest is deleted from the live object. The manifests therefore mirror the live spec exactly, including operator-defaulted fields; I checked this programmatically (the only difference is the new parameter).
storageClassstays unset, as it is live. The GitRepo haskeepResources: true.Follow-up PR will add Barman Cloud ObjectStore + ScheduledBackup (needs DataKnifeAI/gitops-core#7).
Made with Cursor