-
Notifications
You must be signed in to change notification settings - Fork 67
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Proxy configuration is not honored by image-reflector-controller
#322
Comments
The same here, seems the wget pod using is from busybox and that version ignored the no_proxy environment variables |
To configure HTTP/S proxies please see https://fluxcd.io/flux/cheatsheets/bootstrap/#using-https-proxy-for-egress-traffic |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The
image-reflector-controller
adds the followingstatus
to anImageRepository
:All components within the
flux-system
go their proxy settings injected bykyverno
as follows:HTTP_PROXY
HTTPS_PROXY
NO_PROXY
http_proxy
https_proxy
no_proxy
The same environment variables and as they are injected, work on all other Pods, except
flux
Pods. For example, when called fromflux
controller pods, usingwget example.com
results in400 Bad Request
from the proxy server. Going into allflux
Pods, I can confirm thatenv
prints the proper proxy settings. This issue withwget
may be related to Alpine #10446 or Docker Alpine #51.The
context deadline exceeded
above may suggest that theimage-reflector-controller
does not use the proxy settings after all.Does the
image-reflector-controller
support proxy settings? And if so, how?(I found evidence for that in the
source-controller
but not here.)The text was updated successfully, but these errors were encountered: