davidgibbons opened a new issue, #367: URL: https://github.com/apache/superset-kubernetes-operator/issues/367
## Problem Structured metastore configuration supports `passwordFrom`, but `host`, `port`, and `username` are literals. This does not compose with Kubernetes-native database provisioning: the database endpoint is only known after reconciliation and is commonly published in a Secret. `uriFrom` requires a single preassembled URI Secret, which is not always practical when a provisioner deliberately owns endpoint data and credentials in separate Secrets. ## Requested interface Add optional SecretKeySelector counterparts for structured connection fields, for example `hostFrom`, `portFrom`, and `usernameFrom`. Each field should be mutually exclusive with its literal counterpart. The operator should inject the selected values as `valueFrom.secretKeyRef` into every Python component and lifecycle Job, retaining the existing runtime URI assembly and ensuring values never enter the generated ConfigMap. ## Compatibility This is additive: existing `host`, `port`, `username`, and `passwordFrom` behavior should remain unchanged. ## Current workaround Omit `spec.metastore`, add explicit Secret key references through `spec.podTemplate.container.env`, and set `SQLALCHEMY_DATABASE_URI` in raw `spec.config`. It works, but bypasses the typed metastore interface and its validation. -- 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
