Upgrading Notes

To 21.0.0

This major release updates the PostgreSQL subchart to its newest major 11.x.x, which contain several changes in the supported values (check the upgrade notes to obtain more information).

Upgrading Instructions

To upgrade to 21.0.0 from 20.x, it should be done reusing the PVC(s) used to hold the data on your previous release. To do so, follow the instructions below (the following example assumes that the release name is odoo and the release namespace default):

1. Obtain the credentials and the names of the PVCs used to hold the data on your current release:

    export ODOO_PASSWORD=$(kubectl get secret --namespace default odoo -o jsonpath="{.data.odoo-password}" | base64 --decode)
    export POSTGRESQL_PASSWORD=$(kubectl get secret --namespace default odoo-postgresql -o jsonpath="{.data.postgresql-password}" | base64 --decode)
    export POSTGRESQL_PVC=$(kubectl get pvc -l app.kubernetes.io/instance=odoo,app.kubernetes.io/name=postgresql,role=primary -o jsonpath="{.items[0].metadata.name}")
   

2. Delete the PostgreSQL statefulset (notice the option –cascade=false) and secret:

    kubectl delete statefulsets.apps --cascade=false odoo-postgresql
    kubectl delete secret odoo-postgresql --namespace default
   

3. Upgrade your release using the same PostgreSQL version:

    CURRENT_PG_VERSION=$(kubectl exec odoo-postgresql-0 -- bash -c 'echo $BITNAMI_IMAGE_VERSION')
    helm upgrade odoo bitnami/odoo \
      --set odooPassword=$ODOO_PASSWORD \
      --set postgresql.image.tag=$CURRENT_PG_VERSION \
      --set postgresql.auth.password=$POSTGRESQL_PASSWORD \
      --set postgresql.persistence.existingClaim=$POSTGRESQL_PVC
   

4. Delete the existing PostgreSQL pods and the new statefulset will create a new one:

    kubectl delete pod odoo-postgresql-0
   

19.0.0

The Bitnami Odoo image was refactored and now the source code is published in GitHub in the rootfs folder of the container image repository.

Upgrading Instructions

To upgrade to 19.0.0 from 18.x, it should be done enabling the “volumePermissions” init container. To do so, follow the instructions below (the following example assumes that the release name is odoo and the release namespace default):

1. Obtain the credentials and the names of the PVCs used to hold the data on your current release:

    export ODOO_PASSWORD=$(kubectl get secret --namespace default odoo -o jsonpath="{.data.odoo-password}" | base64 --decode)
    export POSTGRESQL_PASSWORD=$(kubectl get secret --namespace default odoo-postgresql -o jsonpath="{.data.postgresql-password}" | base64 --decode)
    export POSTGRESQL_PVC=$(kubectl get pvc -l app.kubernetes.io/instance=odoo,app.kubernetes.io/name=postgresql,role=primary -o jsonpath="{.items[0].metadata.name}")
   

2. Upgrade your release:

    helm upgrade odoo bitnami/odoo \
      --set odooPassword=$ODOO_PASSWORD \
      --set postgresql.auth.password=$POSTGRESQL_PASSWORD \
      --set postgresql.persistence.existingClaim=$POSTGRESQL_PVC \
      --set volumePermissions.enabled=true
   

Full compatibility is not guaranteed due to the amount of involved changes, however no breaking changes are expected aside from the ones mentioned above.

To 18.0.0

This version standardizes the way of defining Ingress rules. When configuring a single hostname for the Ingress rule, set the ingress.hostname value. When defining more than one, set the ingress.extraHosts array. Apart from this case, no issues are expected to appear when upgrading.

To 17.0.0

On November 13, 2020, Helm v2 support was formally finished, this major version is the result of the required changes applied to the Helm Chart to be able to incorporate the different features added in Helm v3 and to be consistent with the Helm project itself regarding the Helm v2 EOL.

What changes were introduced in this major version?

• Previous versions of this Helm Chart use apiVersion: v1 (installable by both Helm 2 and 3), this Helm Chart was updated to apiVersion: v2 (installable by Helm 3 only). Here you can find more information about the apiVersion field.
• Move dependency information from the requirements.yaml to the Chart.yaml
• After running helm dependency update, a Chart.lock file is generated containing the same structure used in the previous requirements.lock
• The different fields present in the Chart.yaml file has been ordered alphabetically in a homogeneous way for all the Bitnami Helm Chart.
• Additionally updates the PostgreSQL subchart to its newest major 10.x.x, which contains similar changes.

Considerations when upgrading to this version

• If you want to upgrade to this version using Helm v2, this scenario is not supported as this version does not support Helm v2 anymore.
• If you installed the previous version with Helm v2 and wants to upgrade to this version with Helm v3, please refer to the official Helm documentation about migrating from Helm v2 to v3.

Useful links

• Bitnami Tutorial
• Helm docs
• Helm Blog

Upgrading Instructions

To upgrade to 17.0.0 from 16.x, it should be done reusing the PVC(s) used to hold the data on your previous release. To do so, follow the instructions below (the following example assumes that the release name is odoo and the release namespace default):

1. Obtain the credentials and the names of the PVCs used to hold the data on your current release:

    export ODOO_PASSWORD=$(kubectl get secret --namespace default odoo -o jsonpath="{.data.odoo-password}" | base64 --decode)
    export POSTGRESQL_PASSWORD=$(kubectl get secret --namespace default odoo-postgresql -o jsonpath="{.data.postgresql-password}" | base64 --decode)
    export POSTGRESQL_PVC=$(kubectl get pvc -l app.kubernetes.io/instance=odoo,app.kubernetes.io/name=postgresql,role=master -o jsonpath="{.items[0].metadata.name}")
   

2. Delete the PostgreSQL statefulset (notice the option –cascade=false):

    kubectl delete statefulsets.apps --cascade=false odoo-postgresql
   

3. Upgrade your release:

    helm upgrade odoo bitnami/odoo \
      --set odooPassword=$ODOO_PASSWORD \
      --set postgresql.auth.password=$POSTGRESQL_PASSWORD \
      --set postgresql.persistence.existingClaim=$POSTGRESQL_PVC
   

4. Delete the existing PostgreSQL pods and the new statefulset will create a new one:

    kubectl delete pod odoo-postgresql-0