Locales table in PostgreSQL without any record on container creation


  • Used Zammad version: 6.0.0-127
  • Used Zammad installation type: helm to Kubernetes

Is this a BUG REPORT or FEATURE REQUEST? (choose one):

Version of Helm and Kubernetes:
Kubernetes v1.26
Helm v3.12.3

What happened:
When installing Zammad and its dependencies using the helm in Kubernetes, the tables with the languages were created in the installation of Zammad in Kubernetes, but without any records.

What you expected to happen:
That in the standard installation, the table is already loaded in PostgreSQL with the available languages.

How to reproduce it (as minimally and precisely as possible):
An installation of Zammad using Helm, following the following commands:

Add Helm repo

$ helm repo add zammad Zammad Helm chart | zammad-helm

Install / Upgrade Zammad

$ helm upgrade --install zammad zammad/zammad --namespace=zammad

Did you run a clean install without data migration or did you migrate data to your helm chart after installation?

The knowledge_base_locales are only populated when adding a new language to your knowledge base. It has nothing to do with the selection you’re seeing in the UI.

The empty locale table is more of a Problem.
In the railsserver container run rails c

In the rails console run


This will do what the container usually should do on startup already and populate the translation and locale table. Note that somewhere in Zammad 6.0 there where issues when trying to use the the rails console with docker based installation.
Consider updating to the latest 6.0 tag available or possibly even 6.1 which has been released last week.

Maybe that helps already.