You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While that resolves the issue, there is still a misleading warning that shows up warning about a key that has no effect.
WARNING: There are "resources" sections in the chart not set. Using "resourcesPreset" is not recommended for production. For production installations, please set the following values according to your workload needs:
- postgresql.resources
The text was updated successfully, but these errors were encountered:
Thank you for bringing this issue to our attention. We appreciate your involvement! If you're interested in contributing a solution, we welcome you to create a pull request. The Bitnami team is excited to review your submission and offer feedback. You can find the contributing guidelines here.
Your contribution will greatly benefit the community. Feel free to reach out if you have any questions or need assistance.
Name and Version
kubeapps-17.1.1
What architecture are you using?
amd64
What steps will reproduce the bug?
What do you see instead?
This does NOT work as documented. The solution is in #31265 which is to set it under the primary: key (or readReplicas according to https://github.com/bitnami/charts/blob/main/bitnami/postgresql/values.yaml)
e.g.
While that resolves the issue, there is still a misleading warning that shows up warning about a key that has no effect.
The text was updated successfully, but these errors were encountered: