Skip to content
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

Open
jseiser opened this issue Jul 10, 2020 · 6 comments
Open

No Documentation on Using S3 #168

jseiser opened this issue Jul 10, 2020 · 6 comments

Comments

@jseiser
Copy link
Contributor

jseiser commented Jul 10, 2020

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.

@erezo9
Copy link
Contributor

erezo9 commented Aug 19, 2020

@jseiser
don't know if matters but had the same issue
what i did is did export command on my current installation, that gave me all the needed environment variables to give in the extra environment variables in the chart

@ttr
Copy link

ttr commented Aug 27, 2020

@jseiser It should work if you keep MinIO disabled in chart.
It should load your config from DB, and verify if your MM settings for file storage are your own S3.

IAM would need to be done externally, but MM needs only standards aws s3 access keys.

@rrey
Copy link
Contributor

rrey commented Oct 25, 2020

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 ?

@erezo9
Copy link
Contributor

erezo9 commented Oct 25, 2020

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) ?

You can specify a custom service account, but that wont help cause mattermost will not read from that

Does mm support using the pod credentials for the s3 access ?

As far as I know, the only way is via environment variables
the only way is to add an environment variable and probably add via an additional volume mount which is provided via a secret
you can read that here
https://docs.mattermost.com/administration/config-settings.html

@rrey
Copy link
Contributor

rrey commented Oct 25, 2020

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.
I found this issue that talks about that. I'll continue the discussion there.

@cpanato
Copy link
Contributor

cpanato commented Jun 14, 2021

@jseiser are you willing to propose a PR to add this?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants