Feature Request: Add mattermostEnv environment variables to init containers

[paddatrapper]

Feature Request: Add mattermostEnv environment variables to init containers

[mjnagel]

@paddatrapper I have done this in the past to override the init container:

spec:
  podExtensions:
    initContainers:
      - command:
           - /bin/sh
           - -c
           - until pg_isready --dbname="$DB_CONNECTION_CHECK_URL"; do echo waiting for database; sleep 5; done;
         image: postgres
         name: db-readiness-check
         env:
           - name: DB_CONNECTION_CHECK_URL
              valueFrom:
                secretKeyRef:
                  key: DB_CONNECTION_CHECK_URL
                  name: 'my-db-secret'
  database:
    disableReadinessCheck: true

In your case you could reference a secret with the username/password for your DB and change the command to utilize those ENVs. I may have gotten some of the indentation off since I was copying this over from another format inside of a helm chart. Hope this helps...its pretty simple to make a "clone" of the default init container and then modify as you need.

[paddatrapper]

Adding to that, it would be great if Mattermost interpreted environment variables in the connection string correctly, so that this worked in the mattermost container too.

[Szymongib]

Hey @paddatrapper,

I do not think we would like to pass those envs to the Init Containers as they are meant to be specific for Mattermost.

What you can do tho, is to define your own init containers for which you can define your own envs:

apiVersion: installation.mattermost.com/v1beta1
kind: Mattermost
metadata:
  name: mm-example-anywhere
spec:
  ...
  podExtensions:
    initContainers:
      - [YOUR CONTAINER DEFINITION HERE]

[paddatrapper]

Are those extensions patched in or does it require a full definition of the initContainer?

[Szymongib]

They require full definition, you can probably copy the default one and adjust.

[paddatrapper]

Hmm... It seems this is pointless until mattermost supports interpreting the environment variables within the connection string anyway. Thanks for the guidance!