You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Then delete the mattermost-operator pod. Allowing new one to spin up
mysql db instances are created
Expected behavior
A minio tenant should be created and used for mattermost deployment
Observed behavior (that appears unintentional)
Minio tenant is not being created. Below is the log from mattermost operator:
time="2024-01-02T17:59:33Z" level=error msg="[opr.controller.mattermost] Reconciler error" error="failed to check Minio instance: no matches for kind "MinIOInstance" in version "miniocontroller.min.io/v1beta1"" name=mattermost namespace=mattermost-operator reconciler group=installation.mattermost.com reconciler kind=Mattermost
Possible fixes
Most Likely there have been changes in the minio operator which are not accounted for by mattermost operator.
Like this comment in an issue minio/operator#94 (comment)
Below is my yaml for the deployment of mattermost
apiVersion: installation.mattermost.com/v1beta1kind: Mattermostmetadata:
name: mattermost # Chose the desired namespec:
size: 500users # Adjust to your requirementsingress:
enabled: truehost: asdasd.fereee.gi # Adjust to your domainannotations:
kubernetes.io/ingress.class: nginxdatabase:
operatorManaged:
replicas: 3resources:
requests:
cpu: 500mmemory: 500MistorageSize: 20Gitype: mysqlelasticSearch: {}fileStore:
operatorManaged:
replicas: 2resources:
requests:
cpu: 200mmemory: 500MistorageSize: 50Giversion: 6.0.1licenseSecret: ""# If you have created secret in step 1, put its name here
The text was updated successfully, but these errors were encountered:
Summary
Unable to deploy matter most with minio as storage.
Steps to reproduce
Install the operator via
Then installed mysql operator
Then install the minio operator
Then delete the mattermost-operator pod. Allowing new one to spin up
mysql db instances are created
Expected behavior
A minio tenant should be created and used for mattermost deployment
Observed behavior (that appears unintentional)
Minio tenant is not being created. Below is the log from mattermost operator:
time="2024-01-02T17:59:33Z" level=error msg="[opr.controller.mattermost] Reconciler error" error="failed to check Minio instance: no matches for kind "MinIOInstance" in version "miniocontroller.min.io/v1beta1"" name=mattermost namespace=mattermost-operator reconciler group=installation.mattermost.com reconciler kind=Mattermost
Possible fixes
Most Likely there have been changes in the minio operator which are not accounted for by mattermost operator.
Like this comment in an issue minio/operator#94 (comment)
Below is my yaml for the deployment of mattermost
The text was updated successfully, but these errors were encountered: