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

fix(NRC): find all node IPs for NAT exclusion #1779

Merged
merged 1 commit into from
Dec 13, 2024
Merged

Conversation

aauren
Copy link
Collaborator

@aauren aauren commented Dec 10, 2024

@zerkms @mrueg @twz123 @rbrtbnfgl

Back in commit 9fd46cc when I was pulling out the krnode struct I made a mistake in the syncNodeIPSets() function and didn't grab the IPs of all nodes, instead I only grabbed the IP of the current node multiple times.

This caused other nodes (besides the current one) to get removed from the kube-router-node-ips ipset which ensures that we don't NAT traffic from pods to nodes (daemons and HostNetwork'd items).

This should fix that problem.

Fixes #1778

Back in commit 9fd46cc when I was pulling out the krnode struct I made a
mistake in the `syncNodeIPSets()` function and didn't grab the IPs of
all nodes, instead I only grabbed the IP of the current node multiple
times.

This caused other nodes (besides the current one) to get removed from
the `kube-router-node-ips` ipset which ensures that we don't NAT traffic
from pods to nodes (daemons and HostNetwork'd items).

This should fix that problem.
@aauren aauren merged commit 6ce2c6d into master Dec 13, 2024
7 checks passed
@aauren aauren deleted the fix_ipip_node_nat branch December 13, 2024 15:22
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

Successfully merging this pull request may close these issues.

Connectivity through ipip is broken since 2.3.0
1 participant