-
Notifications
You must be signed in to change notification settings - Fork 145
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
No Documentation on Using S3 #168
Comments
@jseiser |
@jseiser It should work if you keep MinIO disabled in chart. IAM would need to be done externally, but MM needs only standards aws s3 access keys. |
Am I wrong or the chart is missing a way to specify a custom service account that could be set on the deployment to provide the credentials for s3 ? (on AWS for instance) ? Does mm support using the pod credentials for the s3 access ? |
You can specify a custom service account, but that wont help cause mattermost will not read from that
As far as I know, the only way is via environment variables |
Thanks for the feedback. I want to use a service account to avoid providing any credential from environment and benefit from the AWS role mechanism. |
@jseiser are you willing to propose a PR to add this? |
There is nothing indicating this chart can be used directly with S3. Ive merged in changes to be able to provide the service account the ability to handle IAM Access, but Im still not able to find enough documentation to actually configure this to store its data on an S3 bucket.
Our existing MM installation runs on EC2, with the /data folder on S3 and DB on RDS, we want to migrate to MM on Kubernetes and just keep using what we already have.
The text was updated successfully, but these errors were encountered: