-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
calico-node use problem #9349
Comments
if the cube-02 ip a show is blew, the pod ipv6 ping normal |
but if cube-02 is this, cube-02 pod ipv6 can not ping to other node and the src address become 2024:1011::1111 |
and the calico-node log show the change |
why this will happen? calico-node why always choose the first int6 address? |
why calico-node always use the first int6 to as the ipv6 src address
Expected Behavior
the pod ipv6 ping normal
Current Behavior
i have three kubernetes node cluster, use dulstack, and the ingress-nginx use a ipv6 address bind to cube-02, but i found if the ipv6 vip set in the node ipv6 front, the cube-02 can not ping the other node pod ipv6, if the cube-02 node ipv6 in front the vip ipv6, the route is right? why?
Possible Solution
Steps to Reproduce (for bugs)
Context
Your Environment
The text was updated successfully, but these errors were encountered: