Rename storageAutoscaling to storageScaling in values and templates#813
Merged
jvpasinatto merged 4 commits intopercona:mainfrom Mar 9, 2026
Merged
Rename storageAutoscaling to storageScaling in values and templates#813jvpasinatto merged 4 commits intopercona:mainfrom
storageAutoscaling to storageScaling in values and templates#813jvpasinatto merged 4 commits intopercona:mainfrom
Conversation
Contributor
Author
|
This should fix #812 |
Contributor
|
@amerello could you please update README as well? |
… references in `psmdb-db` README
Contributor
Author
Contributor
|
thanks @amerello. Could you also bump the field |
jvpasinatto
approved these changes
Mar 9, 2026
Contributor
|
Thanks for the contribution @amerello! |
Contributor
Author
Thank you for the quick review! |
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.
The psmdb-db chart was rendering the field storageAutoscaling in the PerconaServerMongoDB custom resource, but the operator expects storageScaling. This caused autoscaling configurations to be ignored.
Solution:
Updated charts/psmdb-db/templates/cluster.yaml to use the correct storageScaling field in the rendered output.
Renamed .Values.storageAutoscaling to .Values.storageScaling in values.yaml and the template for consistency.