-
Notifications
You must be signed in to change notification settings - Fork 85
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
Curl to nginx/test fails works only once for each node #110
Comments
Hi, I'm really busy right now, working on a new release |
Hi! Yes it still doesn't work reliably:
What's also odd, is, that after I booted up the cluster this time (I switched it off after my last post), it seems like not everything was restarted on the first node:
kube-config info (I needed to sudo that) shows:
Proxy logs from node 2:
Proxy logs from master:
Hope this helps... |
I ran into the same issue.. at first networking services were working fine but now it seems to be broken:
All kube-system stuff is running. I set up kubeadm to use flannel.
Any idea what could be the problem? |
I actually realized the problem is only with the worker nodes i added to the cluster |
So what isn't working? |
Hi!
I installed Kubernetes on ARM via Package Deployment on a present Raspbian install (1 master and 2 worker).
Besides modifying /boot/cmdline.txt and resolv.conf (as described in #106) I think I did not do anything different than descibed in the readme.
I end up with:
pi@k8sn1:~ $ curl 10.0.0.138
WELCOME TO NGINX
pi@k8sn1:~ $ curl 10.0.0.138
WELCOME TO NGINX
pi@k8sn1:~ $ curl 10.0.0.138
WELCOME TO NGINX
pi@k8sn1:~ $
pi@k8sn1:~ $ curl 10.0.0.138
curl: (7) Failed to connect to 10.0.0.138 port 80: Connection timed out
I am new to Kubernetes, so I am not sure where to look further. To me it looks as it could be a load balancer problem.
Could you point me in the right direction? Let me know if you need anything else for sorting this out.
Thanks! :-)
The text was updated successfully, but these errors were encountered: