Option to disable proxy

[skaegi]

We just installed with the operator and noticed that we had several operator-proxy-webhooks running. This is not providing functionality that we want in our cluster and were surprised that the operator installed it. We expected the operator to just help us with managing the lifecycle of our Tekton components and not add functionality.

Could we please have an option to remove it from our config.

[vdemeester]

@skaegi the proxy webhook is basically a no-op, and the admission controller should only be registered if there is a proxy setup (aka the operator having a non-empty http_proxy/… set of environment variables. At least that's how it should work.
This means the operator-proxy-webhooks pod is basically doing nothing, which I think, we could avoid indeed (either smartly or not).

/cc @piyush-garg

[tekton-robot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale with a justification.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close with a justification.
If this issue should be exempted, mark the issue as frozen with /lifecycle frozen with a justification.

/lifecycle stale

Send feedback to tektoncd/plumbing.

[vdemeester]

/lifecycle frozen

[vdemeester]

Putting this into the roadmap as it can get in the way under heavy load.
The proxy should be disabled by default if there is no proxy configured.

[vdemeester]

Also related to #2470