elasticsearch-init also /opt/zammad/storage

[klml]

What this PR does / why we need it

After a restart zammad-0 -c elasticsearch-init had an error Read-only file system /opt/zammad/storage

E, [2023-09-20T04:04:01.548417#9-6180] ERROR -- : Unable to send Ticket.find(290).search_index_update_backend backend: #<Errno::EROFS: Read-only file system @ dir_s_mkdir - /opt/zammad/storage>

this was already suggested in #214, which introduced /opt/zammad/storage in all containers and all initContainers

But #214 was superseded by #215, which introduced /opt/zammad/storage only in all containers, but not in initContainers.

I am not sure if we need /opt/zammad/storage in all initContainers, but for sure in elasticsearch-init.

Which issue this PR fixes

• fixes Unable to restart due elasticsearch-init container #212

Checklist

• Chart Version bumped
• Upgrading instructions are documented in the README.md

[mgruner]

@klml this looks awesome. Would you be so kind to rebase please, f41b98d should hopefully fix the failing chart linting checks.

I would also suggest to go a step further: in all places where /opt/zammad/var is mounted, /opt/zammad/storage should be mounted as well. This is to provide a consistent environment for Zammad containers.

[mgruner]

I would also suggest to go a step further: in all places where /opt/zammad/var is mounted, /opt/zammad/storage should be mounted as well. This is to provide a consistent environment for Zammad containers.

One small correction: it would not be needed for containers that don't run the Zammad stack, but only need /opt/zammad/var to check for the zammad.ready file which signals that the zammad-init container finished, like the zammad-nginx container. But I would add it to all other places which run the Zammad code.

[klml]

We have 4 init containers (currently all without /opt/zammad/storage), we need it in for sure in elasticsearch-init.
We dont need it in zammad-init.

So only postgresql-init and zammad-volume-permissions is left. I am not sure if /opt/zammad/storage is needed there.

[mgruner]

I have to correct myself. The postgresql-init container does run the Zammad stack, so it should also get /storage. And zammad-init does not run the stack right now, but I would still add it there for consistency reasons. Would you be able to add this? Otherwise, I can do a follow-up.

[klml]

@mgruner now we have /opt/zammad/storage and and /opt/zammad/var in all containers, except zammad-volume-permissions.

[mgruner]

👏 thanks a lot @klml