How to View Kubernetes Pod Logs Files With Kubectl #443
-
The kubectl logs command show "dial tcp: lookup xxx on xxx:53: no such host" |
Beta Was this translation helpful? Give feedback.
Answered by
prometherion
Apr 22, 2024
Replies: 1 comment
-
This is the typical issue you're facing when the Tenant Control Plane has no connectivity to Services deployed in the tenant worker nodes, and that's common. If you haven't, you have to enable the Konnectivity addon for your TCPs which will instruct the Kubernetes API Server on how to reach out to the Services deployed in the cluster. If this doesn't work, you could need to fine-tune the kubelet's preferred address type. |
Beta Was this translation helpful? Give feedback.
0 replies
Answer selected by
prometherion
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This is the typical issue you're facing when the Tenant Control Plane has no connectivity to Services deployed in the tenant worker nodes, and that's common.
If you haven't, you have to enable the Konnectivity addon for your TCPs which will instruct the Kubernetes API Server on how to reach out to the Services deployed in the cluster.
If this doesn't work, you could need to fine-tune the kubelet's preferred address type.