Align production Redis PVC size - #2406
Merged
Merged
Conversation
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.
What changed
1Gito8Gi.Why
The live Redis PVCs were expanded to 8Gi through KubeBlocks, but the committed manifest still requested 1Gi. KubeBlocks interpreted that drift as an unsupported volume shrink and stopped reconciliation, which prevented later Redis resource updates from reaching the InstanceSet and pods.
Matching the manifest to the live PVC size removes the invalid shrink request and allows normal reconciliation. This does not shrink, migrate, or recreate the existing volumes.
Validation
git diff --checkk8s/ex-prod-redis.yamlsuccessfully with PyYAML1Gito8Gistorage request changekubectl apply --dry-run=clientwas not available because the read-only Kubernetes wrapper blocks allapplyoperations, including client-side dry runs.Breaking changes
None.