[I] feat(k8s): make app-tier object storage configurable via storage.s3 [texera]

["aicam (via GitHub)" <gi...@apache.org>]

aicam opened a new issue, #5931:
URL: https://github.com/apache/texera/issues/5931

   ### Task Summary
   
   Route the Texera application services' object-storage access through a configurable `storage.s3` values block, instead of hardcoding the in-cluster MinIO Service and Secret. This is the **app-tier slice** of making object storage pluggable (parent feature #5891); LakeFS/Lakekeeper storage and the `minio.enabled` off-switch follow as a separate step.
   
   Scope (this task):
   - Add a `storage.s3` block to `values.yaml` (`endpoint`, `region`, `existingSecret`, `accessKeyId`, `secretAccessKey`).
   - Add chart helpers that resolve the S3 endpoint and credentials Secret, defaulting to the in-cluster MinIO when `storage.s3.endpoint` is empty.
   - Add a gated `s3-credentials-secret.yaml` (rendered only for an external endpoint without a pre-existing Secret).
   - Wire `file-service` and `workflow-computing-unit-manager` to the helpers.
   
   Non-goals (deferred to the next step):
   - LakeFS blockstore + Lakekeeper warehouse external-S3 wiring.
   - `minio.enabled` toggle to drop the in-cluster MinIO entirely.
   - `values-aws.yaml` example overlay.
   
   ### Task Type
   
   - [x] Refactoring / enabler (no behavior change by default)
   - [ ] Bug fix
   - [ ] Documentation
   
   The default (on-prem / in-cluster MinIO) install renders an identical set of resources; the external-S3 path is opt-in via `storage.s3.endpoint`.
   
   Part of #5891. Follows #5757 (template reorg) and #5641 (design discussion).
   


-- 
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: notifications-unsubscribe@texera.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

Re: [I] feat(k8s): make app-tier object storage configurable via storage.s3 [texera]

["github-actions[bot] (via GitHub)" <gi...@apache.org>]

github-actions[bot] commented on issue #5931:
URL: https://github.com/apache/texera/issues/5931#issuecomment-4791930701

   <!-- texera:template-compliance -->
   👋 Thanks for opening this issue, @aicam!
   
   It looks like the issue description doesn't quite follow our template yet:
   
   - This issue doesn't appear to use one of our templates (Bug, Feature, or Task). Please open it using a template so the required details are captured.
   
   Filling out the template helps reviewers understand and triage your contribution faster. Please edit the description to complete it. This message will disappear automatically once the template is followed.
   
   You can find the template prompts by editing the description, or see [CONTRIBUTING.md](https://github.com/apache/texera/blob/main/CONTRIBUTING.md) for the full contribution flow.
   


-- 
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: notifications-unsubscribe@texera.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

Re: [I] feat(k8s): make app-tier object storage configurable via storage.s3 [texera]

["aicam (via GitHub)" <gi...@apache.org>]

aicam closed issue #5931: feat(k8s): make app-tier object storage configurable via storage.s3
URL: https://github.com/apache/texera/issues/5931


-- 
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: notifications-unsubscribe@texera.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org