GKE is our "new cluster".
Before GKE, our stack ran on mesos+marathon cluster on GCE with weave for
networking.
We still have some services "left behind" on the "old cluster", so I ran
into this when trying to access an "old service" from a "new service".
Not surprisingly, this does not work when t
We're you testing weave or running g it for real?
On Jul 4, 2017 7:28 AM, "Itamar O" wrote:
> solved it.
> I found a collision in the routing table of the 10.240.0.2 host...
> # route
> Kernel IP routing table
> Destination Gateway Genmask Flags Metric RefUse
> Iface
> de
solved it.
I found a collision in the routing table of the 10.240.0.2 host...
# route
Kernel IP routing table
Destination Gateway Genmask Flags Metric RefUse
Iface
default 10.240.0.1 0.0.0.0 UG0 00 eth0
*10.32.0.0 * 2
here's a slightly redacted snippet of my GCP routes:
> gcloud compute routes list
NAME NETWORK
DEST_RANGE NEXT_HOP
PRIORITY
default-route-2aab1c1d780bf8ed datalab 10.240.0.0/24 1000
default-route-91098cb127e5377bdefault 10.
Check for duplicate or overlapping routes in the cloud console?
On Jul 2, 2017 9:14 AM, "Itamar O" wrote:
> Hi,
> I'm investigating a weird routing behavior on our production GKE cluster
> (nodes & master running 1.6.6), not quite sure how to proceed at this point.
>
> The essence of the issue:
Hi,
I'm investigating a weird routing behavior on our production GKE cluster
(nodes & master running 1.6.6), not quite sure how to proceed at this point.
The essence of the issue: containers on the GKE cluster can communicate
with *some* GCE instances, but *not others*, and there's no (apparent)
d
