diff --git a/stable/odoo/Chart.yaml b/stable/odoo/Chart.yaml index 930697fc5c..4a7fedafb8 100644 --- a/stable/odoo/Chart.yaml +++ b/stable/odoo/Chart.yaml @@ -1,6 +1,6 @@ apiVersion: v1 name: odoo -version: 11.1.9 +version: 11.1.10 appVersion: 12.0.20191015 description: A suite of web based open source business apps. home: https://www.odoo.com/ diff --git a/stable/odoo/README.md b/stable/odoo/README.md index 8fc7285237..b4129ca9e2 100644 --- a/stable/odoo/README.md +++ b/stable/odoo/README.md @@ -31,7 +31,7 @@ To install the chart with the release name `my-release`: $ helm install --name my-release stable/odoo ``` -The command deploys Odoo on the Kubernetes cluster in the default configuration. The [configuration](#configuration) section lists the parameters that can be configured during installation. +The command deploys Odoo on the Kubernetes cluster in the default configuration. The [Parameters](#parameters) section lists the parameters that can be configured during installation. > **Tip**: List all releases using `helm list` @@ -45,7 +45,7 @@ $ helm delete my-release The command removes all the Kubernetes components associated with the chart and deletes the release. -## Configuration +## Parameters The following table lists the configurable parameters of the Odoo chart and their default values. @@ -135,29 +135,34 @@ $ helm install --name my-release -f values.yaml stable/odoo > **Tip**: You can use the default [values.yaml](values.yaml) +## Configuration and installation details + ### [Rolling VS Immutable tags](https://docs.bitnami.com/containers/how-to/understand-rolling-tags-containers/) It is strongly recommended to use immutable tags in a production environment. This ensures your deployment does not change automatically if the same tag is updated with a different image. Bitnami will release a new chart updating its containers if a new version of the main container, significant changes, or critical vulnerabilities exist. +### Using an external database + +Sometimes you may want to have Odoo connect to an external database rather than installing one inside your cluster, e.g. to use a managed database service, or use a single database server for all your applications. To do this, the chart allows you to specify credentials for an external database under the [`externalDatabase` parameter](#parameters). You should also disable the PostgreSQL installation with the `postgresql.enabled` option. For example using the following parameters: + +```console +postgresql.enabled=false +externalDatabase.host=myexternalhost +externalDatabase.user=myuser +externalDatabase.password=mypassword +externalDatabase.port=3306 +``` + +Note also if you disable PostgreSQL per above you MUST supply values for the `externalDatabase` connection. + ## Persistence The [Bitnami Odoo](https://github.com/bitnami/bitnami-docker-odoo) image stores the Odoo data and configurations at the `/bitnami/odoo` path of the container. Persistent Volume Claims are used to keep the data across deployments. This is known to work in GCE, AWS, and minikube. -See the [Configuration](#configuration) section to configure the PVC or to disable persistence. - -## Using an external database - -Sometimes you may want to have Odoo connect to an external database rather than installing one inside your cluster, e.g. to use a managed database service, or use a single database server for all your applications. To do this, the chart allows you to specify credentials for an external database under the [`externalDatabase` parameter](#configuration). You should also disable the PostgreSQL installation with the `postgresql.enabled` option. For example: - -```console -$ helm install stable/odoo \ - --set postgresql.enabled=false,externalDatabase.host=myexternalhost,externalDatabase.user=myuser,externalDatabase.password=mypassword,externalDatabase.port=3306 -``` - -Note also if you disable PostgreSQL per above you MUST supply values for the `externalDatabase` connection. +See the [Parameters](#parameters) section to configure the PVC or to disable persistence. ## Upgrading