Skip to content
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

Merged
merged 8 commits into from
Oct 22, 2020
Merged

[bitnami/odoo] Odoo major #4071

merged 8 commits into from
Oct 22, 2020

Conversation

joancafom
Copy link
Contributor

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

  • commonAnnotations
  • commonLabels
  • extraVolumes
  • extraVolumeMounts
  • podAnnotations
  • podLabels
  • podSecurityContext
  • containerSecurityContext
  • affinity
  • podAffinityPreset
  • podAntiaffinityPreset
  • nodeAffinityPreset
  • nodeSelector
  • tolerations
  • sidecars
  • initContainers
  • extraEnvVars
  • extraEnvVarsCM
  • extraEnvVarsSecret
  • command
  • args
  • resources
  • customLivenessProbe
  • customReadinessProbe
  • existingSecret

Checklist

  • Chart version bumped in Chart.yaml according to semver.
  • Variables are documented in the README.md
  • Title of the PR starts with chart name (e.g. [bitnami/chart])
  • If the chart contains a values-production.yaml apart from values.yaml, ensure that you implement the changes in both files

⚠️ Keep in mind that if you want to make changes to the kubeapps chart, please implement them in the kubeapps repository. This is only a synchronized mirror.

Copy link
Contributor

@dani8art dani8art left a 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
Copy link
Contributor

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?

Copy link
Contributor Author

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.

@joancafom joancafom merged commit 995715d into bitnami:master Oct 22, 2020
@joancafom joancafom deleted the odoo-major branch October 22, 2020 11:37
garettmd pushed a commit to garettmd/odoo that referenced this pull request Jan 31, 2024
…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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants