Configure the UATs to run behind a proxy

[NohaIhab]

Context

This is the tracking issue for configuring the UATs behind proxy.
We need to be able to run the UATs behind proxy in order to test the bundle in that environment.

What needs to get done

1. Running using Notebook: Configure the UATs to run behind a proxy #95
2. Running using driver: Configure the UATs to run behind a proxy #96
3. Fix KSVC failed to start behind proxy with RevisionFailed reason: failed to resolve image to digest knative-operators#204

Definition of Done

UATs can be run behind proxy

[syncronize-issues-to-jira]

Thank you for reporting us your feedback!

The internal ticket has been created: https://warthogs.atlassian.net/browse/KF-5945.

This message was autogenerated

[kimwnasptd]

A note that we are also documenting how to spin-up the proxy environment in
canonical/bundle-kubeflow#990

[NohaIhab]

Summary

Completed work

• Explore running the UATs behind proxy #76 - The exploration issue contains a lot of context on the design and the issues discovered.
• Issue KSVC failed to start behind proxy with RevisionFailed reason: failed to resolve image to digest knative-operators#204 affecting KNative and KServe, the fixes are in:
  • fix: configure proxy env vars storage init container kserve-operators#257
  • fix: configure proxy env vars in serving controller  knative-operators#208

Work in progress

• backporting of fix: configure proxy env vars storage init container kserve-operators#257 and fix: configure proxy env vars in serving controller  knative-operators#208
• Running using Notebook: Configure the UATs to run behind a proxy #95
• Running using driver: Configure the UATs to run behind a proxy #96

Todo

• fix issue TFJob failed to run behind proxy with IOError: Not a gzipped file training-operator#182 blocking TFJobs UATs - I expect this is an issue with our current UATs for TFJob not being able to pick up the proxy envs, not an issue with training operator itself.