Proposal

The current AuthenticationRef spec limits KEDA to a set of primitives such as HashiCorpVault, ConfigMap, Secret, various Cloud Provider auth mechanism and the likes. However, an often used pattern is sharing credentials via a tmpfs-backed emptyDir where an initContainer is responsible for obtaining and decrypting the secret and shares it with the main process via the filesystem. E.g. using the Vault Agent Injector.

Use-Case

We use a custom solution that needs to share secrets via a memory-backed file with KEDA

Is this a feature you are interested in implementing yourself?

Yes

Anything else?

No response