The Tekton operator manages most of the components in tekton ecosystem. Day by day customers are asking for a way to supply custom changes in their environment based on their needs (like updating configmap, args of a container, etc.,). Right now they can be achieved partially by hacking in different ways(mostly in installersets). however Operator reconciles and reverts back those changes after some time. 

Later, based on the impact we are working on the operator code base to support the custom changes from TektonConfig CR. It leads to us spending our time on those requests more frequently and at the same time the customer has to wait for a long period of time to get the build with the feature support.

Most of the time our workarounds are hacking installersets. So it is happening without tekton operator knowledge (kind of backdoor operation). Hence I am proposing a generic solution to address these kinds of problems from TektonConfig CR.