Mike Zappa
Mike Zappa
@aojea Since the kubelet calls the CRI-API Status RPC: https://github.com/containerd/containerd/blob/6333db77015764f7d45b407094a3bc2cc05c239b/internal/cri/server/status.go#L49 Kubelet: https://github.com/kubernetes/kubernetes/blob/3718932d9a3ea459217ca11efe1ae9ead6aa92c1/pkg/kubelet/kubelet.go#L2886 The Status returning an error will set the node to not ready. I did notice after about 2...
> Hi @MikeZappa87, do you plan to work on this? If not, I can try to work on it as a new contributor. Hello, I need to finish this up....
@squeed just want to get this to the top of your email
I am going to run a few more tests with this code in containerd. As of now all tests have been successful.
@AkihiroSuda I made a few updates. I have squashed the commits.
@mikhail5555 how did you go about testing this?
I noticed that we have two groups of 9 successful pings. Is that continuous? The first successful ping of the second group was 488ms as well. I wonder if that...
Are you able to share your set up? Are you using containerd as a container runtime or are you using docker? "On linux, by default, when you create a container,...
Is the issue only with 169.254.169.254? Does this happen with the others below?: 169.254.169.123 169.254.169.249 169.254.169.250 169.254.169.251 169.254.169.253 Do you have layer 2 connectivity for 10.102.28.65? Are you running that...
Have you tried the latest AWS AMI? We had a conversation with AWS and they were changing this behavior.