https://github.com/imio/helm-odoo
Helm Chart for Odoo
https://github.com/imio/helm-odoo
devops helm helm-chart kubernetes odoo
Last synced: about 2 months ago
JSON representation
Helm Chart for Odoo
- Host: GitHub
- URL: https://github.com/imio/helm-odoo
- Owner: IMIO
- License: apache-2.0
- Created: 2024-12-17T09:44:25.000Z (over 1 year ago)
- Default Branch: main
- Last Pushed: 2026-04-15T09:31:00.000Z (2 months ago)
- Last Synced: 2026-04-15T10:38:59.764Z (2 months ago)
- Topics: devops, helm, helm-chart, kubernetes, odoo
- Language: Shell
- Homepage:
- Size: 42 KB
- Stars: 10
- Watchers: 2
- Forks: 7
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
# Helm Chart for Odoo
[](https://opensource.org/licenses/Apache-2.0)   
## Introduction
This [Helm](https://helm.sh/) chart installs `Odoo` in a [Kubernetes](https://kubernetes.io/) cluster.
> [!IMPORTANT]
> This helm chart is designed for @IMIO specific needs and is not intended to resolve all use cases. But we are open to contributions and suggestions to improve this helm chart.
> This Helm chart targets Odoo 16.0+ using the official Odoo Docker image. The default image tag is `18.0`; override with `image.tag` as needed.
## Prerequisites
> [!NOTE]
> For production environments, it is recommended to use [CloudNativePG](https://github.com/cloudnative-pg/cloudnative-pg) for PostgreSQL. The bundled chart is primarily intended for testing and development purposes. Be also aware of the upcoming changes to the bitnami catalog described in this [issue](https://github.com/bitnami/containers/issues/83267).
- Kubernetes cluster 1.25+
- Helm 3.8.0+
- PV provisioner support in the underlying infrastructure.
- Postgres DB (This chart can install a postgresql database based on the bitnami/postgresql chart). We use it for testing purposes.
## Why do we not use the bitnami/odoo chart?
- we want to use the official Odoo Docker Image or our custom Odoo Docker Image.
- we need some specific configuration for our Odoo instance.
## Installation
### Pull Helm release
```bash
helm repo add imio https://imio.github.io/helm-charts
helm repo update
```
### Configure the chart
The following items can be set via `--set` flag during installation or configured by editing the `values.yaml` directly (need to download the chart first).
See the [values.yaml](values.yaml) file for more information.
### Install the chart
```bash
helm install [RELEASE_NAME] imio/odoo
```
or by cloning this repository:
```bash
git clone https://github.com/imio/helm-odoo.git
cd helm-odoo
helm dep up
helm upgrade odoo . -f values.yaml --namespace odoo --create-namespace --install
```
## Configuration
The following table lists the configurable parameters of the helm-odoo chart and the default values.
See the [values.yaml](values.yaml) file for more information.
### Use an existing Secret for Odoo configuration
You can use an existing secret for the Odoo configuration.
In the `values.yaml` file, set the `existingSecret.enabled` parameter to `true`.
Then, create a Secret in your namespace named `-odoo-conf`
(or `-odoo-conf` if `fullnameOverride` is set), containing
the `odoo.conf` key.
### Use external-secrets.io for Odoo configuration
In the `values.yaml` file, set the `externalsecrets.enabled` parameter to `true`.
You need to have the external-secrets.io operator installed in your cluster. See the [external-secrets.io documentation](https://external-secrets.io/latest/) for more information.
> [!WARNING]
> `existingSecret.enabled` and `externalsecrets.enabled` are mutually exclusive.
> Enabling both will cause `helm install`/`helm upgrade` to fail with an explicit error.
> Choose exactly one secret backend, or leave both disabled to have the chart generate secrets from `values.yaml`.
## Local Setup for development
Create a kind cluster:
```bash
cat <