IPv6 networking: mention --flannel-ipv6-masq in dual stack and single stack ipv6 section #330
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.