New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[bitnami/wordpress] Appears that "global.storageClass" overrides more specific storageClass settings #24845
Comments
Hi! Thank you so much for reporting. The logic is set here: https://github.com/bitnami/charts/blob/main/bitnami/common/templates/_storage.tpl#L16 Would you like to submit a PR changing the default behavior? |
Sure, I can try and come up with one. |
This fixes bitnami#24845 as we now prefer the more specific option over the global option, rather than the other way around.
This fixes bitnami#24845 as we now prefer the more specific option over the global option, rather than the other way around. Signed-off-by: James Tocknell <aragilar@gmail.com>
This fixes bitnami#24845 as we now prefer the more specific option over the global option, rather than the other way around. Signed-off-by: James Tocknell <aragilar@gmail.com>
#24863 created with the smallest change I think will fix this. |
Thank you so much for the PR! The team will take a look |
This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback. |
Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary. |
Name and Version
wordpress:21.0.10
What architecture are you using?
amd64
What steps will reproduce the bug?
Setting
global.storageClass
to a dummy fallback value (e.g. "test-storage-class") overrides the storageClass used in more specific places (e.g. for wordpress,mariadb.primary.persistence.storageClass
andpersistence.storageClass
). I would expect global to act as a fallback, rather than override the values.Are you using any custom parameters or values?
No response
What is the expected behavior?
I would expect to be able to use a fallback value in global, so as to be able to catch any cases where the default storage class is being used, and direct them to a more appropriate class.
What do you see instead?
My settings of
mariadb.primary.persistence.storageClass
andpersistence.storageClass
are ignored, andglobal.storageClass
is used instead.Additional information
No response
The text was updated successfully, but these errors were encountered: