Skip to content

Support S3 credentials through a secret #37

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

Closed
fhennig opened this issue Mar 28, 2022 · 0 comments
Closed

Support S3 credentials through a secret #37

fhennig opened this issue Mar 28, 2022 · 0 comments
Assignees

Comments

@fhennig
Copy link
Contributor

fhennig commented Mar 28, 2022

We want an s3 section in the CRD, for now we can use the same structure as in druid:

s3:
  endpoint: s3-de-central.profitbricks.com
  credentialsSecret: s3-credentials

for the endpoint there is a configoption, the access key and secret key should be mounted from the referenced secret. The secret structure used in druid is:

apiVersion: v1
kind: Secret
metadata:
  name: s3-credentials
stringData:
  accessKeyId: YOURACCESSKEYIDHERE
  secretAccessKey: YOURSECRETACCESSKEYHERE

The secret should be mounted and the env vars for that are AWS_ACCESS_KEY_ID AWS_SECRET_ACCESS_KEY. The secret also needs to be mounted in the executors, so they can read from S3 too; so the pod template needs to be adjusted accordingly.

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

Successfully merging a pull request may close this issue.

2 participants