Config map names should be customizable, or at least prefixable

[abayer]

Expected Behavior

The various config maps used by Tekton Pipeline (config-artifact-bucket, config-logging, etc) should be able to be given custom names, to avoid potential collisions with other services.

Actual Behavior

They can't. =)

Steps to Reproduce the Problem

1. Change the name of one of the config maps.
2. Anything referring to that config map won't work.

Additional Info

For the standard usage, this isn't a problem, since the config maps go into the tekton-pipelines namespace, but in Jenkins X, we put everything in the jx namespace along with...lots of other junk. It'd be really handy if we could at the least prefix the config map names to guarantee uniqueness. I haven't thought through the implementation details, but maybe something like an optional argument to the controller and webhook to provide a prefix for the various config map names would work.

[abayer]

Looks like the prefix idea would be a challenge for config-observability since that config map is only referenced from knative.dev/pkg code...

[bobcatfish]

I think we'd be open to this if anyone wants to do the work!

[dibyom]

/assign @jerop

[tekton-robot]

@dibyom: GitHub didn't allow me to assign the following users: jerop.

Note that only tektoncd members, repo collaborators and people who have commented on this issue/PR can be assigned. Additionally, issues/PRs can only have 10 assignees at the same time.
For more information please see the contributor guide

In response to this:

/assign @jerop

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[jerop]

@dibyom and I looked into this, and found that all config maps are customizable except for feature-flags config map which is fixed in #2363

the other config maps had be fixed in #1723