...
Any value property set in application application.yaml file and not re-defined in Helm profile is still loaded and kept unchanged. There is no need to duplicate the properties in Helm profile.
Detailed configuration:
...
For example see CPS Core:
3. Helm Values Level
Finally, still when deploying CPS application in a specific user environment, the user can to provide its own custom helm overrides values to customize the application in any specific target environment.
When doing this the user is still able to provide and set any additional application property he needs. Such properties are added under following properties paths:
config.additionaProperties.*for any additional application or Spring property to be addedconfig.eventPublisher.*for Kafka custom configuration properties (if ONAP Strimzi Kafka is not used)
These properties paths are automatically added to the Spring Helm profile by following Helm templating:
- https://github.com/onap/oom/blob/jakarta/kubernetes/cps/components/cps-core/resources/config/application-helm.yml#L66
- https://github.com/onap/oom/blob/jakarta/kubernetes/cps/components/cps-core/resources/config/application-helm.yml#L62
Detailed configuration:
...
For example, see CPS Core:
- https://github.com/onap/oom/blob/jakarta/kubernetes/cps/components/cps-core/values.yaml#L199
- https://github.com/onap/oom/blob/jakarta/kubernetes/cps/components/cps-core/values.yaml#L193
The values above are specified in the OOM CPS values file, but the user is still able to also create and provide its own overrides values file to be used when deploying.