-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
Route NAT64 to NAT Gateway in IPv6 public topology #12843
Conversation
e615689
to
63e8272
Compare
63e8272
to
2b47019
Compare
/test pull-kops-e2e-ipv6-calico |
/cc @olemarkus |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: olemarkus The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/lgtm cancel There seems to be quite a few timeouts in that calico test. |
It might need DNS64 |
This was missing DNS64, that just merged. Calico IPv6 test failed as any other test because of IRSA. Let's see it #12766 fixes it. |
Yep. That should be merged now, so I'll retest when the current run fails. |
Doesn't look like it worked... |
2b47019
to
0d2e9dc
Compare
/test pull-kops-e2e-ipv6-calico |
NAT64 works on my cluster. Rebasing and retesting. |
Did you try creating an EBS volume on your cluster, just to confirm that it works? |
I don't have IRSA turned on for this cluster. I can hit the global and regional STS endpoints, though. Ping through NAT64 to one public IP wasn't working, though. I need to bisect that a bit. |
I can ping the IPv6 addresses of nodes in other AZs and an IPv6 address in the public Internet, both from the node and from a non-host-network pod. I cannot ping through NAT64, though I can connect with HTTPS. |
The retest failed as well. I cannot test IRSA in my environment without going through extraordinary effort. Could someone else try this out? |
/test pull-kops-e2e-ipv6-cilium |
@johngmyers: The following tests failed, say
Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
0d2e9dc
to
da2b33a
Compare
I think we might want to land this as-is, then separately look into why IRSA is still failing. |
/lgtm |
Issue with IRSA comes from a bug in AWS EBS CSI driver. Setting
|
No description provided.