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
{{ message }}
This repository was archived by the owner on Dec 16, 2021. It is now read-only.
I have upgrade the helm release with the above added to the YAML. But I don't see the SQS ARN being created when I check the logs of the pod. The minio service is working - but the SQS ARN does not seem to be created.
I am also trying to enable kafka notification for buckets.
helm/charts@3c06eb4 - says
To update your Minio server configuration while it is deployed in a release, you need to
helm inspect values stable/minio.minio_server_configsettings in a YAML formatted file, and then pass that file like thishelm upgrade -f config.yaml stable/minio.Git comments also say:
minio_server_config:
config.json: |
{
"region": "us-east-1",
"browser": "on",
"logger": {
"console": {
"enable": true
},
"file": {
"enable": false,
"filename": ""
}
},
"notify": {
"kafka": {
"1": {
"enable": true,
"brokers": ["kafka:9092"],
"topic": "minio-topic"
}
}
}
}
I have upgrade the helm release with the above added to the YAML. But I don't see the SQS ARN being created when I check the logs of the pod. The minio service is working - but the SQS ARN does not seem to be created.
Is there a sample on how to do this?