When using kubectl logs to view the kube-proxy pod logs on the agent node received a "400 Bad Request" error #6846
Replies: 1 comment 1 reply
-
If you'd pulled the kubelet and containerd logs before restarting things, we might have been be able to figure out why it was unable to read logs from that container. Unfortunately there's not much to be done now. |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Environmental Info:
RKE2 Version: v1.26.15+rke2r1
Cluster Configuration: 3 servers + n agents
Describe the bug:
In my Rancher, I found that I could not view the kube-proxy pod logs of the agent nodes through the "View Logs" feature (it shows disconnected), but I can view the kube-proxy pod logs of the server node normally.
After that, I tried to view the kube-proxy pod logs on the agent nodes using kubectl -n kube-system logs kube-proxy-xxx from the server node, but it didn't work either.
However, when I logged into the agent node and used crictl log, I could view the logs normally, so the issue seems to be on the Kubernetes level.
After I restarted the rke2-agent and recreated the kube-proxy pod, everything returned to normal.
Beta Was this translation helpful? Give feedback.
All reactions