@Brutus5000 requested this feature to make managing secrets easier in kubernetes. This way values like the database password which are never going to change dynamically anyway can be stored in a Secret object and mapped to the environment while non-sensitive data can be stored in a ConfigMap and mapped to a volume that will be able to trigger the dynamic changes. Since kubernetes doesn't really support merging those two things into a single file, this feature will make setting up the configuration a lot easier and more idiomatic.
NOTE: This will only work for values which are expected to be strings! This should not be a problem since this feature is only intended to be used for passwords.
@Brutus5000 requested this feature to make managing secrets easier in kubernetes. This way values like the database password which are never going to change dynamically anyway can be stored in a
Secret
object and mapped to the environment while non-sensitive data can be stored in aConfigMap
and mapped to a volume that will be able to trigger the dynamic changes. Since kubernetes doesn't really support merging those two things into a single file, this feature will make setting up the configuration a lot easier and more idiomatic.NOTE: This will only work for values which are expected to be strings! This should not be a problem since this feature is only intended to be used for passwords.