mengw15 commented on code in PR #5932:
URL: https://github.com/apache/texera/pull/5932#discussion_r3508574111
##########
bin/k8s/values.yaml:
##########
@@ -65,6 +65,18 @@ postgresql:
initdb:
scriptsConfigMap: "postgresql-init-script"
+# Object storage (S3) used by the Texera services. Leave storage.s3.endpoint
+# empty to use the in-cluster MinIO (the `minio:` block below). Set it to an
+# S3-compatible endpoint URL -- together with region and credentials -- to
+# point the services at an external store (e.g. AWS S3) instead.
+storage:
+ s3:
+ endpoint: "" # "" => in-cluster MinIO; otherwise an S3 endpoint
URL
+ region: "us-west-2"
+ existingSecret: "" # existing Secret with access-key-id /
secret-access-key; "" => chart creates one
+ accessKeyId: ""
+ secretAccessKey: ""
Review Comment:
Forward-looking note (out of scope for this PR): static long-lived IAM keys
in a K8s Secret work, but are a step behind current EKS best practice (IRSA —
projected ServiceAccount token → STS short-lived creds, no static key
anywhere). IRSA is EKS-specific and doesn't fit a chart that also targets
on-prem, so this is a thought for the AWS-focused follow-up (values-aws.yaml
overlay?), not a change to this PR.
If this direction feels valid, could you open a TODO issue so it doesn't get
lost when the AWS overlay work starts?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
