We currently
There are four ways to provide configuration to helm when deploying
Current Approach
...
Introduction
Currently, the default application configuration is present inside the docker images . It and it gets overridden when it is deployed using the helm. The issue with this approach is duplication and
- maintaining same values at two places
- the possibility of missing a few configurations in the OOM
...
- having obsolete values in OOM
To avoid it, we can keep only keep those properties in the OOM which needs to change be changed based on deployment and provide an ability for overriding any property if required.
Possible Solutions
In any spring application, application properties can be provided in multiple ways, which are mentioned below in ascending order of priority.
- application.yml in the resources folder
- application-<profile>.yml in the resources folder
- environment variables
- system property to JVM using -Dkey=value
The one at th
Use environment variables