Urgent: Missing Odoo 18.0 Docker image tag 18.0.20250305 — Production Impact

[CybrosysAssista]

Name and Version

bitnami/odoo 18.0.20250305

What steps will reproduce the bug?

1. Create a new namespace in Kubernetes:
   kubectl create namespace odoo-one

2. Attempt to install Odoo Helm chart with the missing image:

    helm install odoo-one oci://registry-1.docker.io/bitnamicharts/odoo \
     --namespace odoo-one \
     --create-namespace \
     --set image.tag=18.0.20250305
   

3. Helm pulls the chart successfully, but Kubernetes fails to pull the Docker image.

4. Error occurs:

   Failed to pull image "docker.io/bitnami/odoo:18.0.20250305": rpc error: code = NotFound desc = failed to pull and unpack image ... not found

Are you using any custom parameters or values?

--set image.tag=18.0.20250305

No other custom values.yaml used.

What is the expected behavior?

Kubernetes should be able to pull the Odoo 18.0 image successfully, deploy the pods, and start the Odoo services as normal.

What do you see instead?

The image pull fails because the Docker image tag 18.0.20250305 is missing.
Currently, only older versions (13.0, 12.0, 11.0) exist on Docker Hub.
All other versions, including 18.0, are unavailable.
This prevents deployment of production services.

Additional information

• Helm chart: bitnamicharts/odoo
• Docker Hub URL: https://hub.docker.com/r/bitnami/odoo/tags
• Impact: High — production services are failing to deploy/restart
• Error message: Failed to pull image ... not found
• Kubernetes and Helm versions: (optional, can include your cluster details)
• Urgency: Critical, needs immediate attention to restore the missing image or provide a replacement tag

[carrodher]

With the changes announced at #35164, the container images were removed from docker.io/bitnami and moved to docker.io/bitnamilegacy, where they will no longer receive updates. To continue getting new, hardened image versions, a Bitnami Secure Images subscription is required.

See the pinned issue linked above for full details.

[nyghtly-derek]

Hello @CybrosysAssista, this is because VMWare pay-walled the bitnami/ images in docker, which are pulled by these helm charts. You can continue to use the helm chart, but you'll need to overwrite the image pulls to use an alternative image. In the short term you can just use bitnamilegacy/odoo.

Here's an example of overwriting the helm chart, but please keep in mind that the charts are all slightly different, so the exact override will also be different. Don't give up, though. There are many other users going through the same migration right now. It just takes a little bit of work to figure out and then you want have to pay a subscription to VMWare.

[github-actions]

This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.

[github-actions]

Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.