-
Notifications
You must be signed in to change notification settings - Fork 9.3k
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/odoo] Odoo major #4071
Conversation
Signed-off-by: joancafom <[email protected]>
Improve README structure Bump PostgreSQL version Signed-off-by: joancafom <[email protected]>
Signed-off-by: joancafom <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great job! LGTM with a minor comment, just out of curiosity.
* Now the upgrade works | ||
|
||
```console | ||
$ helm upgrade odoo bitnami/odoo --set odooPassword=$ODOO_PASSWORD --set postgresql.postgresqlPassword=$POSTGRESQL_PASSWORD |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Didn"t you need the existing PVC to upgrade postgres?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, but there is no need to specify it as in the previous step we have used --cascade=false
with PostgreSQL. This way, the old pod (and the PVC) is preserved. Then, when the pod is deleted, a new one with the correct labels comes up and automatically re-uses the same PVC. Think of it as a failing pod that is re-scheduled by K8s, it will reuse the PVC 😄
This was derived from the upgrading instructions in PostgreSQL Chart itself.
…ami#4071) * Update PostgreSQL Req file Signed-off-by: joancafom <[email protected]> * Change labels and annotations Improve README structure Bump PostgreSQL version Signed-off-by: joancafom <[email protected]> * Add standardizations Signed-off-by: joancafom <[email protected]> * Add externalSecret support * Add commonAnnotations to ingress * Improve NOTES * Bump Chart and README upgrade details * Fix indentation issues
Description of the change
This PR updates PostgreSQL subchart to the new major version, which includes breaking changes. More info at #3021
As this requires a major bump in this chart, it has been adapted to follow some standardizations found in other Bitnami Charts. Please check additional information or README for a detailed list of new standard features.
The most important change is in the labels, that are adapted to follow the Helm charts standard labels.
Benefits
Standardization, up-to-date subcomponents,
Possible drawbacks
Breaks backwards compatibility
Applicable issues
NA
Additional information
Checklist
Chart.yaml
according to semver.[bitnami/chart]
)values-production.yaml
apart fromvalues.yaml
, ensure that you implement the changes in both files