Integration
This is an IBM Automation portal for Integration products. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).
Shape the future of IBM!
We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:
Search existing ideas
Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,
Post your ideas
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
Specific links you will want to bookmark for future use
Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.
IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.
ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.
Thank you for this idea.
Post discussion in our 3iab (13 November 2024), we have concluded that this idea is viable and feasible for an epic in our roadmap.
For prior art see Cloudera's approach https://docs.cloudera.com/csa/1.11.1/security/topics/csa-encrypt-tool-security.html.
See also
kubernetes.env.secretKeyRefandkubernetes.secretsin https://nightlies.apache.org/flink/flink-docs-master/docs/deployment/config/#flink-configuration-file.https://cwiki.apache.org/confluence/display/FLINK/FLIP-161%3A+Configuration+through+envrionment+variables was closed for what seems like a bad reason.
We'd probably want a FLIP allowing flink-conf.yaml values to reference either env vars or keys within yaml files on disk, so as to leverage the two kubernetes.* properties referenced above.
Note that the Flink operator publishes flink-config.yaml into a config map before mounting it into Flink pods. It's not enough to change the
FlinkDeploymentCR to be able to reference properties from secrets, because they'd just be published in plain text within the resulting configmap.