Skip to content
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 settings not pulled when using node-joiner.sh #9045

Open
maxisses opened this issue Sep 20, 2024 · 2 comments
Open

Proxy settings not pulled when using node-joiner.sh #9045

maxisses opened this issue Sep 20, 2024 · 2 comments

Comments

@maxisses
Copy link

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.

@maxisses maxisses changed the title Proxy settings Proxy settings not pulled when using node-joiner.sh Sep 20, 2024
@thikade
Copy link

thikade commented Oct 9, 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.

@andfasano
Copy link
Contributor

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).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants