Doc note: developers need to provide whatever settings can be made globally via TektonConfig and then we can add them to the "configuring using TektonConfig" chapter.

Epic Goal

Setting proxy env vars should be done through podTemplates (TEP-101) instead of directly on the taskrun pods.

Why is this important?

Reduce the overhead of watching resources

Acceptance Criteria (Mandatory)

When proxy settings are available, they are passed to TaskRun pods through podTemplates

Open questions::

• Could the proxy env vars be set within the default podTemplate in config-defaults configmap?
  https://tekton.dev/docs/pipelines/install/#customizing-basic-execution-parameters

h2. Done Checklist
* Acceptance criteria are met
* Non-functional properties of the Feature have been validated (such as performance, resource, UX, security or privacy aspects)
* User Journey automation is delivered
* Support and SRE teams are provided with enough skills to support the feature in production environment