Geek Answers Handbook

Unable to resolve host name using `kubectl logs` or` kubectl exec`

I created a Kubernetes cluster using CoreOS on AWS and I am unable to contact the nodes from the wizard.

For example, operations like kubectl exec or kubectl logs cause an error similar to the following:

 Error from server: dial tcp: lookup ip-XXX-X-XXX-XXX.eu-west-1.compute.internal: no such host

I found some problems on Github that describe the problem, so I know that the team knows about this error, but I would like to ask here whether it is possible to use some workaround until it works out in some way.

One workaround was to use the --hostname-override flag, but since I'm on AWS, this flag is ignored (see # 22984 )

Related issues on GitHub: # 22770 # 22063 .

+7
kubernetes coreos
source share
1 answer

Are you sure you are using the right context?

 kubectl config use-context my-cluster-name
+1
source share

More articles:


All Articles