Add support for HTTP proxy during deployment about atmosphere HOT 4 CLOSED

@gtirloni Would this #579 be solution, we only use internet for Authentication and Monitoring all else come from internally.

from atmosphere.

@mpiscaer I think that's a good start but there are many places that this touches. Basically all helm values need some kind of custom value to point it to the new registry with authentication (common in more restricted environments).

Yes, I think it's a good start. I was confusing this issue with another one about authenticated container registries.

from atmosphere.

The step one to solving this was this commit:

vexxhost/ansible-collection-containers@1480d52

The step two is documenting the necessary variable, in 99.9999% of the cases, it will be:

http_proxy: "http://foobar:3128"
https_proxy: "http://foobar:3128"
no_proxy: "localhost,127.0.0.0/8,172.16.0.0/12,192.168.0.0/16,169.254.0.0/16,.svc,.cluster.local"

With this, I believe that covers almost all scenarios unless you've got some wild stuff running your cluster on non private IP space WITH an HTTP proxy...

from atmosphere.

Documented here and tested working.

https://vexxhost.github.io/atmosphere/deploy/inventory.html#http-proxy

from atmosphere.