Workaround for K8s dual stack bug #733
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
edwarnicke
force-pushed
the
tunnelip_to_ipv6
branch
2 times, most recently
from
c08af4d
to
dce7f04
Compare
K8s doesn't have a functioning way to get the IPv6 Pod IP via the downward API. This hacks around it if env variable NSM_TUNNEL_IP_TO_V6 = true The first GlobalUnicast IPv6 address from the same kernel interface as the IPv4 Tunnel IP is used instead. Signed-off-by: Ed Warnicke <[email protected]>
edwarnicke
force-pushed
the
tunnelip_to_ipv6
branch
from
dce7f04
to
0fdf3b9
Compare
nsmbot
pushed a commit
that referenced
this pull request
Jul 14, 2023
…k-vpp@main PR link: networkservicemesh/sdk-vpp#733 Commit: ad8c2ca Author: Artem Glazychev Date: 2023-07-14 17:21:48 +0700 Message: - Revert "Add pinggrouprange to forwarder's chain (#718)" (#733) This reverts commit ce2e514e2a71b25b450d83af3c7209e396b77122. Signed-off-by: NSMBot <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
K8s doesn't have a functioning way to get the IPv6 Pod IP via the
downward API.
This hacks around it if env variable
NSM_TUNNEL_IP_TO_V6 = true
The first GlobalUnicast IPv6 address from the same kernel interface as
the IPv4 Tunnel IP is used instead.
Signed-off-by: Ed Warnicke [email protected]