This message was deleted.

Are you running

kubectl logs

? You can check your connection with

kubectl cluster-info

.

do you have enough permission to access this pod?

@refined-analyst-8898 when I execute cluster info Kubernetes control plane is running at https://127.0.0.1:6443 CoreDNS is running at https://127.0.0.1:6443/api/v1/namespaces/kube-system/services/kube-dns:dns/proxy Metrics-server is running at https://127.0.0.1:6443/api/v1/namespaces/kube-system/services/https:metrics-server:https/proxy

@delightful-pharmacist-29626 I believe you are running

kubectl logs

. Is that accurate? If so, I believe you may be seeing the correct log output from the container. In other words, the error message could be emitted by the container, not

kubectl logs

, and so you could be reading the error message successfully from the pod log and mistaking it to be a problem with reading the log. I believe this is the case because

kubectl logs

will only communicate with the kube-apiserver, and the error message indicates a problem communicating with the node agent, IIUC.

Got it. Thank you