Proxy support for Pipeline *and* tasks

[vdemeester]

Feature request

This is probably worth splitting into two issues, but here goes.

As an admin, I want the tekton controllers installed to use users network proxy settings defined for the platform so that both the tekton controllers as well as the Task or Pipeline steps / user workloads can access images, git repos, etc through our organizations proxy and with custom certificates.

Why is this important?
To enable customer installs of the tekton to have network communications using the to use global proxy settings

Note: this is only for tektoncd/pipeline but it does affect other components (tektoncd/triggers, …). It also, most likely, need to be a TEP I guess.

/cc @sbose78 @afrittoli @bobcatfish

Use case

A user sets up tekton in a cluster that uses a global proxy for network communications. It should work : aka tasks should be able to communicate with the outside world through the proxy (if what is in the tasks supports that of course), the different tekton components should go through the proxy too when doing network query ; for tektoncd/pipeline, it might be when querying the oci registry for the image config, …

Parts

There is actually few parts for that issue :

• How the user can provide the proxy configuration ? (through a configmap seems the best)
• Support for proxy's environment variables inside tektoncd/pipeline code (cmd/controller, cmd/webhook, …)
• How the controller/admission webhook can add those at runtime ? (this requires Provide mechanism to set environment variables on TaskRuns #1606 to work)

[piyush-garg]

/assign

[tekton-robot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
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.

/lifecycle stale

Send feedback to tektoncd/plumbing.

[piyush-garg]

/remove-lifecycle stale

[bobcatfish]

Note we have a start to a TEP about this in tektoncd/community#232

[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.

[tekton-robot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten with a justification.
Rotten issues close after an additional 30d of inactivity.
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 rotten

Send feedback to tektoncd/plumbing.

[tekton-robot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen with a justification.
Mark the issue as fresh with /remove-lifecycle rotten with a justification.
If this issue should be exempted, mark the issue as frozen with /lifecycle frozen with a justification.

/close

Send feedback to tektoncd/plumbing.

[tekton-robot]

@tekton-robot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen with a justification.
Mark the issue as fresh with /remove-lifecycle rotten with a justification.
If this issue should be exempted, mark the issue as frozen with /lifecycle frozen with a justification.

/close

Send feedback to tektoncd/plumbing.

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.