-
Notifications
You must be signed in to change notification settings - Fork 308
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
Make sure the node's IP addresses is set in noProxy #5824
Conversation
c43b488
to
80790ce
Compare
80790ce
to
79612d1
Compare
Hi @votdev, Thanks! |
Relates to: harvester/harvester#5824 Signed-off-by: Volker Theile <vtheile@suse.com>
|
9477113
to
cf05de8
Compare
cf05de8
to
3d0122a
Compare
Relates to: harvester#4282 Signed-off-by: Volker Theile <vtheile@suse.com>
3d0122a
to
b7dec9d
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. Thanks for the PR.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, thanks!
LGTM. |
@Mergifyio backport v1.2 v1.3 |
✅ Backports have been created
|
…arvester#5936) Relates to: harvester#4282 Signed-off-by: Volker Theile <vtheile@suse.com> (cherry picked from commit d06f6a7) Co-authored-by: Volker Theile <vtheile@suse.com>
Problem:
If you configure httpProxy and httpsProxy, you must also put Harvester node's CIDR into noProxy, otherwise, the Harvester cluster will be broken.
Solution:
Add a webhook to validate the user input; it should reject if the node IP is not included in the no_proxy CIDR range.
Related Issue:
#4282
Test plan:
The test plan assumes that several hosts are available in the cluster. For the following test cases, the hosts with the following IP addresses are involved:
Case 1:
Advanced
>Settings
and then selectEdit Settings
forhttp-proxy
.Save
.noProxy should contain the node's IP addresses or CIDR. The node(s) 192.168.0.30, 192.168.0.31, 192.168.0.32 are not covered.
is displayed.Case 2:
Advanced
>Settings
and then selectEdit Settings
forhttp-proxy
.192.168.0.0/27
in theno-proxy
form field.Save
.noProxy should contain the node's IP addresses or CIDR. The node(s) 192.168.0.32 are not covered.
is displayed.Case 3:
Advanced
>Settings
and then selectEdit Settings
forhttp-proxy
.192.168.0.0/24
in theno-proxy
form field.Save
.Settings
page.Case 4:
Advanced
>Settings
and then selectEdit Settings
forhttp-proxy
.192.168.0.30, 192.168.0.31, 192.168.0.32
in theno-proxy
form field.Save
.Settings
page.