v1.Node ended with: an error on the server
kaykhan opened this issue · 0 comments
Hi friends,
Our pods went into a state of NodeNotReady, i noticed the kube-proxy running on the node at that particular time reported a few errors:
kubectl -n kube-system get logs kube-proxy-lrxpq
W0618 06:26:51.892869 1 reflector.go:347] vendor/k8s.io/client-go/informers/factory.go:150: watch of *v1.Node ended with: an error on the server ("unable to decode an event from the watch stream: got short buffer with n=0, base=4092, cap=40960") has prevented the request from succeeding
Can you help me understand abit more about this error and if these errors were the cause of the node being in a NotReady state. Also how i might be able to investigate further
The node did recover after 10-15 minutes, although we experienced some outage due to our pods reporting Node is not ready
AWS Kubernetes EKS: 1.26