Allow custom db check init container image

[mattermost]

Allow custom db check init container image

[Szymongib]

Thanks for reporting the issue.

I think if we provide the ability to override the image I can see people wanting to modify the command also.
If we would like to go with that, maybe we could take the following approach:

apiVersion: installation.mattermost.com/v1beta1
kind: Mattermost
...
spec:
  database:
    readinessCheck:
       initContainers: [Full Containers deffinition here allowing user to override everything (in Go type []v1.Container)]

The readinessCheck is just random name I came up on the spot and we can think of something better, the point is that it will allow user to customise the check further.

In case the readinessCheck would be provided by the user, the operator would not inject the default init containers.

What do you think about this approach? @mjnagel @gabrieljackson

[mjnagel]

That makes sense to me, allowing more customization would be better for future-proofing I'd imagine since someone else could come along and want to customize a different piece of this (command as you mentioned definitely would be a big one).

[mjnagel]

Any progress on this/is help wanted implementing this? This is something we definitely want so that we can override the image (although the additional flexibility to override the entire init container may be nice as well).

[gabrieljackson]

Hey @mjnagel, sorry about the delay on this.

Any progress on this/is help wanted implementing this?

Yes, this is exactly the sort of feature request we would love to have community engagement on. It has been opened as a help wanted ticket and we will add it ourselves in the coming weeks if there are no volunteers.

[Szymongib]

As discussed, picking this one up due to this feature being a higher priority and lack of interest from the community side.