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

IPv6 networking: mention --flannel-ipv6-masq in dual stack and single stack ipv6 section #330

Merged

Conversation

recursivetree
Copy link
Contributor

I run a cluster in dual stack mode using a cidr from the ULA range following the dual stack docs. Using these instructions, I noticed that pods use their pod IP for (cluster-external) outgoing connections, in this case meaning a ULA address, which obviously does not work. What I intended is that they use the host's address. After some googling, I found the --flannel-ipv6-masq option that does what I want. It is documented in the flannel section: https://docs.k3s.io/networking/basic-network-options#flannel-options. However, I think this should also be mentioned in the dual stack and single stack sections, as it is not given that people also read the flannel section.

This PR adds a mention of the need to add --flannel-ipv6-masq if using unroutable IPv6 ranges for a cluster.

I'd argue this use case is relatively common. For example, on many cloud platforms you just get a /64 or even a /128, so using something like ULAs is probablly a must.

@brandond
Copy link
Member

brandond commented Oct 4, 2024

Thanks for the PR! Please sign-off your commit for DCO.

Signed-off-by: recursivetree <recursivetreemail@gmail.com>
@recursivetree recursivetree force-pushed the networking-add-ipv6-masquerade-hint branch from 54e09e2 to 548b99e Compare October 4, 2024 18:22
@recursivetree
Copy link
Contributor Author

Should be done, thanks.

I've also opened an issue because the requirement for Signed-off-by in all commits is not mentioned in this repo: #331

@brandond brandond merged commit b769cb6 into k3s-io:main Oct 4, 2024
3 checks passed
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.

2 participants