John Howard
John Howard
I believe we have tests that exercise this code path, maybe we can add one with multiple gateways
Is this with `cni.ambient.ipv6=true` set or not?
Ok, will try to reproduce myself but in the meantime you probably need that. I am working to make it on-by-default fwiw
I am not entirely sure that will solve it though since this seems like ipv4-in-ipv6 addresses which might need some special consideration. But worth a shot if you have time
Oh interesting, I did not realize the ambient.ipv6 was added after 1.22 and not backported, sorry about the misdirection
I'm planning to try to reproduce this on Monday, but in the meantime if someone can show the pod.status.podIps on the pod and maybe `ip -j addr` it would be...
> Interestingly I'm getting the same issues using 1.22.1, Ambient, and EKS (with Amazon Linux 2 AMIs and IPv4 only subnets). > > No custom configuration on the underlying AMIs...
Ok so based on all the info here I think all the issues are fixed. @bleggett is working to backport from master to 1.22. Anyone seeing these issues can try...
Technically you can simply use `gcr.io/istio-testing/...:latest` but there may have been changes to the install charts, so its best to do the whole thing. In this specific case, there have...
I reproduced it. on master, same EKS setup, with non-distroless images for debugging. `failed to update POD inpod: default/shell-56bd5dbdbf-jxntr failed to add route: permission denied` ``` root@ip-192-168-97-2:/opt/cni/bin# ip route add...