You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using the node-joiner.sh the node-joiner pod is not pulling the cluster-wide proxy settings per default.
A workaround is to modify the script and manually insert the env vars for http, https and noProxy but it would be important to point it out or pull cluster proxy config.
The text was updated successfully, but these errors were encountered:
maxisses
changed the title
Proxy settings
Proxy settings not pulled when using node-joiner.sh
Sep 20, 2024
Stumbled over exactly this today. Note that for me no_proxy also needed to contain kubernetes.default.svc.cluster.local, else the oc cmds inside the node-joiner pod would fail.
The problem has been resolved in 4.17 (see https://issues.redhat.com/browse/OCPBUGS-39090).
Note that the node-joiner script was meant just as a DevPreview only for 4.16, so it's recommended to switch using the oc adm node-image commands introduced since 4.17 (GA version).
When using the node-joiner.sh the node-joiner pod is not pulling the cluster-wide proxy settings per default.
A workaround is to modify the script and manually insert the env vars for http, https and noProxy but it would be important to point it out or pull cluster proxy config.
The text was updated successfully, but these errors were encountered: