You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@fluss.apache.org by "fresh-borzoni (via GitHub)" <gi...@apache.org> on 2026/07/17 16:37:01 UTC

[I] [helm] Declarative secrets support for config provider markers [fluss]

fresh-borzoni opened a new issue, #3686:
URL: https://github.com/apache/fluss/issues/3686

   ### Search before asking
   
   - [x] I searched in the [issues](https://github.com/apache/fluss/issues) and found nothing similar.
   
   
   ### Description
   
   #3658 added config providers, so a server.yaml value can be a ${directory:...} marker instead of a literal secret. But on Kubernetes, actually using that with our chart is still manual: you have to wire extraVolumes, mount the Secret, and hand-write the config.providers lines, including allowed.paths, which is easy to get wrong and is the security guard.
   
   The chart should make this declarative: say which Secrets you want mounted (or injected as env), and get the provider config generated for you, with allowed.paths and the env allowlist derived from what you declared, so the guards are correct by construction and the rendered ConfigMap never contains secret material.
   
   ### Willingness to contribute
   
   - [x] I'm willing to submit a PR!


-- 
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: issues-unsubscribe@fluss.apache.org.apache.org

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


Re: [I] [helm] Declarative secrets support for config provider markers [fluss]

Posted by "fresh-borzoni (via GitHub)" <gi...@apache.org>.
fresh-borzoni closed issue #3686: [helm] Declarative secrets support for config provider markers
URL: https://github.com/apache/fluss/issues/3686


-- 
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: issues-unsubscribe@fluss.apache.org

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