Deploy releases/k8s-manifests 20be7af#142
Merged
Merged
Conversation
This sandbox sees low-demand workloads. 2 instances (1 primary + 1 streaming replica) still gives automated failover; the third replica is unnecessary overhead — saves a pod, ~600Mi RAM, and a 20Gi block storage volume. When scaled down, cnpg will gracefully drain and remove `shared-cluster-3` (the highest-numbered replica). The `shared-cluster-3` PVC is retained per the `linode-block-storage-retain` storage class, in case we ever need to recover the data; can be deleted manually if not needed. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
chore(cnpg): scale shared-cluster from 3 to 2 instances
Author
|
|
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
1 participant
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.
kubectl diffreports that applying 20be7af will change: