-
Notifications
You must be signed in to change notification settings - Fork 469
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
In 1.7.2 cluster created with kops 1.7.0 some pods can't ping other ones #92
Comments
I think that the problem is related to me having 2 subnets, "--zones eu-central-1b,eu-central-1a" it seems that pods in nodes from one subnet cant ping pods from nodes on another subnets |
@felipejfc thanks for trying kube-router. Currently kube-router has limitiation that all nodes need to be L2 adjacent. We need an encapsulation mechansim for connectivity of pods across the nodes in different subnets. I had a bug opened #21 but never had a user asking for that so far. I understand this is common scenario, and really kube-router should support this, I will prioritize and get cross-subnet pod connetivity working. |
- create a ipip tunnel interface from each node to nodes in the different subnet - insert route to local routing table using tunnel device Fixes #92
I tested with images #106 below or the results. I deployed cluster with 1 master 10 nodes ( 5 in us-west-2a, 5 in us-west-2b). US-west-2a nodes in different subnet, and US-west-2b nodes are in different subnet.
Deployed 50 replica sets with 2 replicas of echo server, so there is one pod in each zone. Expose each replica set as node port. and tried to access each node port service twice so as to ensure test access both the pods. So effectivley tested 10 nodes * 50 services * each twice = 1000 node port service access. Each of which succeeded.
|
@felipejfc could you please try deploying cluster with kube-router? Both the issues you reported are fixed and is available in the latest kube-router image. We also did some scaling tests on clusters deployed across multiple zones on AWS. Please see the test results in the bug/pr's. |
Thanks @murali-reddy, I'll try it later! |
I just created a cluster using kops with this line:
And when I enter a kube-dns pod with
it cant ping other kube-dns pods:
I did the test because some pods were having dns lookup errors.
@murali-reddy any hints? Is kube-router compatible with kops 1.7.0 and kubernetes 1.7.2?
The text was updated successfully, but these errors were encountered: