Impact of change frequency
Looking at the configuration knobs from the perspective of frequency of change will help us categorize them between personas defined in the OAM. The change frequency detailing will bring in the discussion of ownership as these perspectives are linked. This section covers change frequency from the perspective of bespoke applications (KRM compliant) and COTS external dependencies (XRM compliant). We can classify configuration change frequency into the following three categories:
- Change very often: Generally, application KRM configuration parameters, such as image tags, release version, environment variables, secrets reference, and application configuration, change very frequently. These configurations are application-centric and owned primarily by the application developers. If we use a template- or DSL-based abstraction, they are good candidates to be exposed as variables. Suppose a plain configuration YAML is used instead of a template- or DSL-based...
