mengw15 commented on PR #6295: URL: https://github.com/apache/texera/pull/6295#issuecomment-4963008521
Agreed on no series-level switch — the overlay is the right profile mechanism at that granularity, and keeping the chart cloud-agnostic argues against an `aws.*` axis anyway. The narrower version of my question is capability-level: right now "where does object storage live" is an emergent property of several keys that must be flipped together — `minio.enabled` gates the component, but the actual routing pivot is `storage.s3.endpoint` presence (what the `texera.s3.*` helpers switch on), with `lakekeeperInit.createBucket`/`flavor` tracking along. The two incoherent combinations render silently: minio off + endpoint unset leaves everything pointing at a nonexistent `<release>-minio`, and minio on + endpoint set gives a half-external install (app tier external, LakeFS still on MinIO). An explicit `objectStorage.mode: internal | external` — or just template-validating the combination — would make those states unrepresentable; the two footguns in my values.yaml comment are reall y symptoms of the missing mode. (The lakefs subchart block stays manual either way, since subchart values can't be derived.) Fine as a follow-up when external S3 graduates. -- 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]
