-
Notifications
You must be signed in to change notification settings - Fork 25
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
No Pod reachable from outside the cluster (Error: 'dial tcp 10.200.57.3:9376: getsockopt: connection timed out') #12
Comments
A
|
Oh, my bad - there´s no
so we can leave that. Also we can leave out |
Is our brave kubernetes-the-hard-way inspired cluster´s apiserver able to connect to the services & pods of our cluster altogether (see kubernetes/dashboard#2340 (comment))??! 😭 |
Seems that using the correct k8s At least using the worker-nodes DNS names directly now gives access to the deployed apps. Accessing This means we are now able to do the first access practice "Access services through public IPs" from https://kubernetes.io/docs/tasks/administer-cluster/access-cluster-services/#accessing-services-running-on-the-cluster. What remains open, is to use the second practice "Access services, nodes, or pods using the Proxy Verb. ", which is more recommended, since API server could do the authentication and authorization. The issue therefore remains open - it seems, that the API server couldn´t connect to the kube-proxy - maybe because, the API server has no access to the Flannel/kube-dns/Docker network (as described here kubernetes/dashboard#2340 (comment))??! |
Created kelseyhightower/kubernetes-the-hard-way#389, as it seems a general design problem of the kubernetes cluster. |
Hmm, seems that Flannel needs to be present on the master nodes: https://stackoverflow.com/a/39179200/4964553 |
…ter nodes, otherwise the kube-apiserver can´t access the services and pods inside the Flannel network on the worker nodes.
Now having Flannel also running on the master nodes, I´am able to access an application inside the Kubernetes cluster after executing the |
See also kubernetes/dashboard#2340 (comment) |
I followed this great hint here
and the instructions in the docs on how to access k8s services from outside, trying to access the k8s service
hostnames
as described inside the Debug Services Guide. I tried to use the following URL to access this service from outside the cluster:This just gives a
503 Service Unavailable
:The text was updated successfully, but these errors were encountered: