MM-16712 Allow specifying number of minio and mysql replicas in ClusterInstallation spec

[jwilander]

https://mattermost.atlassian.net/browse/MM-16712

[jwilander]

Pointing at our Docker image to support standalone Minio until minio/operator#23 is accepted and also until the Minio operator is tagged so we don't have to worry about breaking changes

[gabrieljackson]

Will wait to review until tests pass in case a change is required.

[jwilander]

@cpanato I'm unsure if the tests are failing because of my changes or if the CI machine is just running out of memory, any idea?

[cpanato]

@jwilander checking

[cpanato]

@jwilander the issue is in the tests you are waiting for 1 deployment for minio and mysql but both have 4 pods

•100% ➜ kubectl get pod -n mattermost-operator
NAME                                  READY   STATUS     RESTARTS   AGE
mattermost-operator-8dcb8db6f-hlh9x   1/1     Running    0          7m48s
test-mm-56965bf9cf-nskrq              1/1     Running    0          7m32s
test-mm-minio-0                       1/1     Running    0          7m33s
test-mm-minio-1                       1/1     Running    0          7m17s
test-mm-minio-2                       1/1     Running    0          7m4s
test-mm-minio-3                       1/1     Running    0          6m24s
test-mm-mysql-mysql-0                 4/4     Running    0          7m31s
test-mm-mysql-mysql-1                 4/4     Running    0          5m58s
test-mm-mysql-mysql-2                 4/4     Running    0          3m33s
test-mm-mysql-mysql-3                 0/4     Init:1/2   0          66s

[cpanato]

also in the test you are waiting for deployment and both minio and mysql are not deployments they are statefullsets :)

[cpanato]

The only thing I don't like much is the fork of minio, if that takes longer we will need to maintain our custom fork :/

[gabrieljackson]

👍

[jwilander]

Thanks for the test help @cpanato !