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

pkg/mesh: avoid NAT-ing packets to service CIDRs #351

Merged
merged 2 commits into from
Mar 15, 2023
Merged

Conversation

squat
Copy link
Owner

@squat squat commented Feb 24, 2023

Currently, packets to service CIDRs may be masqueraded because they are
IP addresses that Kilo does not know about and therefore is not sure if
they know about some Kilo IPs, e.g. Peer IPs. This is not terrible but
it is annoying and can prevent some advanced use-cases, see #330. This
commit adds an optional flag to the kg binary that can be given
multiple times to specify the service CIDRs of the cluster so that Kilo
does not masquerade packets to them.

Signed-off-by: Lucas Servén Marín lserven@gmail.com

Currently, packets to service CIDRs may be masqueraded because they are
IP addresses that Kilo does not know about and therefore is not sure if
they know about some Kilo IPs, e.g. Peer IPs. This is not terrible but
it is annoying and can prevent some advanced use-cases, see #330. This
commit adds an optional flag to the `kg` binary that can be given
multiple times to specify the service CIDRs of the cluster so that Kilo
does not masquerade packets to them.

Signed-off-by: Lucas Servén Marín <lserven@gmail.com>
Signed-off-by: Lucas Servén Marín <lserven@gmail.com>
@squat
Copy link
Owner Author

squat commented Mar 13, 2023

Ping @leonnicolas

@squat
Copy link
Owner Author

squat commented Mar 15, 2023

Merging to unblock #330

@squat squat merged commit 79682ce into main Mar 15, 2023
@squat squat deleted the avoid_nat_service_cidr branch March 15, 2023 19:42
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.

None yet

1 participant