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 curl response from pod service #24
Comments
Just figured it out. You run the curl command from one of the nodes. If you did the same as me you ran it on master. Edit: |
This is just a thoery, but I believe the issue here is that there's no external ip address associated with the service:
no external ip, only the cluster ip. You can access it only from the host it's scheduled on. |
This comment has been minimized.
This comment has been minimized.
That website seems to suggest that those ip table rules are to allow the worker nodes to access the public internet via the primary node's internet connection. This was due to their odd networking configuration where the primary node served as a router for the worker nodes. |
You are correct @justinabrahms but they should all be on the sames network in kubernetes so any node should be able to hit a cluster ip, which wasn't happening here. |
Wait... Those may be the wrong commands though.. One moment. Ill double check |
I'm sorry you are right those were the wrong commands. you want these:
|
@DwayneGit Thanks for your response. It seems that setting the iptables to legacy is critical for kubernetes with iptables-1.8.x. Can someone please update the guide on k8s-on-raspbian/GUIDE.md to include this? |
Following the guide in k8s-on-raspbian/GUIDE.md.
When I run:
The HTTP request is sent but it is forever awaiting a response.
Environment
All pods are running
Node (raspberrypi3) successfully joins
I'm using the right port:
Routes show the 31118 port open
Comments
I believe I am missing something very simple. I already tried reset and init and the problem persists.
The text was updated successfully, but these errors were encountered: