solution secret key need to be unique #3315
Description
Description
some solutions use a secret key or similar configuration that should be set uniquely per solution and kept secret, using the default value intact from the values YAML file is considered risky, bad practice.
on some of the solutions (ex. Minio), the values for these secrets are generated via initContainers when not set.
but for other solutions, this is not the case, like in Mastodon, Taiga, and maybe others.
leaving the default values (ex. dummy, etc) is not an option as it is not unique nor secret, either asking the user for a random secret key or something like pair of signing keys is not an option too.
Implementation
my suggestion is to implement an extra step in the Chatflow with such functionality to generate these unique and random values then it overrides the secret values when do helm install.