global cluster http_proxy support / configuration

[xinity]

hello there,

i was wondering what would be the best way to support http_proxy globally ?
i am required to use an internal http_proxy and i want to make sure that all cluster deployed will be able to leverage it

is it something we can achieve using CAPO ?

not sure if it's a CAPO or a CAPI topic to be honest :)

[mdbooth]

I don't think it's either, tbh; I think it's a kubernetes question. I know OpenShift can do this, but I'm not 100% clear on the mechanism. It wouldn't surprise me if it's something like injecting proxy environment variables into all pods on admission.

[jichenjc]

I think it's a k8s question , not something in CPO， so close this and feel free to reopen

not sure whether openshift did something internally through setting on ingress or other things, no clear detail info only how to use it here ...
https://docs.openshift.com/container-platform/4.15/networking/enable-cluster-wide-proxy.html

[pawcykca]

You can achieve this on Node level by:

• image-builder -> preparing images with proxy configuration
• CAPI -> setting proxy configuration in KubeadmControlPlane and KubeadmConfigTemplate

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle rotten
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten