The way to configure values in configMaps like config-defaults, feature-flags etc in compoents are through TektonConfig. 

This approach will work for now but it is becoming difficuly to manage and scale. For each change in any of our component (new field, or deprecating field) we have to change the schema of TektonConfig. This will inturn make it necessary to work on seamless upgrades and docs updates. 

This story is to explore alternate ways to configure values of component configMaps

Acceptance criteria

• A design doc exploring alternative approaches