#541 [Feature] Have cluster resource controller leverage k8s secrets Issue created by katrogan Motivation: Why do you think this is important? In addition to reading substitutable secret values from mounted file paths or injected environment variables, it would be useful to access kubernetes secrets when running the cluster resource controller. Goal: What should the final outcome look like, ideally? It should be possible to inject kubernetes secrets as substitutable template values in the cluster resource controller. Describe alternatives you've considered A clear and concise description of any alternative solutions or features you've considered. Flyte component ☐ Overall ☐ Flyte Setup and Installation scripts ☐ Flyte Documentation ☐ Flyte communication (slack/email etc) ☐ FlytePropeller ☐ FlyteIDL (Flyte specification language) ☐ Flytekit (Python SDK) ☑︎ FlyteAdmin (Control Plane service) ☐ FlytePlugins ☐ DataCatalog ☐ FlyteStdlib (common libraries) ☐ FlyteConsole (UI) ☐ Other [Optional] Propose: Link/Inline If you have ideas about the implementation please propose the change. If inline keep it short, if larger then you link to an external document. Additional context Add any other context or screenshots about the feature request here. Is this a blocker for you to adopt Flyte Please let us know if this makes it impossible to adopt Flyte flyteorg/flyte

#541 [Feature] Have cluster resource controller leverage k8s secrets Issue closed as not planned by github-actions[bot] flyteorg/flyte