Networking TBD.

[timothysc]

This a place marker and TBD.

Currently there is a large gaping hole around the resolution of the GCE network model and the ephemeral re-route model. The closest idea which holds water that I've seen is possibly: https://groups.google.com/forum/#!topic/docker-dev/6tt1y9FTWKg .

But this will indeed affect the slave nodes that the kublet lands on.

[justinholmes]

Why not use openvswitch and gre tunnels?

[timothysc]

Here is a broad overview.
kubernetes/kubernetes#494

[jdef]

related, some recent activity in k8s for service networking, using an IP-per-service model:

• Services v2 (ip-per-service) kubernetes/kubernetes#1402
• https://github.com/GoogleCloudPlatform/kubernetes/blob/master/docs/services.md

will (minimally) require sync'ing our godeps to the latest k8s (probably a good amount of work here)

[jdef]

related docker work to eliminate userland proxies:

• Support hairpin NAT moby/moby#6810
• Make it possible to disable userland proxy moby/moby#8356

[jdef]

Docker is proposing native ovs integration.
moby/moby#8951

[timothysc]

Yeah, I've been tracking. Many of the new proposals could change more then networking.

[jdef]

• proposal in k8s regarding Generic UDP Encapsulation (GUE) / flannel
  Decision: Standardize on Rudder/Flannel for k8s networking? kubernetes/kubernetes#1307

[timothysc]

FWIW, it's my understanding that flannel is a v1 get the ball rolling solution with a plan for replacement.

[jdef]

IP-per-service will land with #102

[timothysc]

@jdef I'm not following the "IP-per-service"?

Latest word on the Docker front was that their networking plugins were due out in ~1-2 Months which will likely ripple all the way through.

[jdef]

I'll have to catch up with docker networking. K8s introduced service
portals in v0.5x. Along with that came ip-per-service and the portal
network. We'll support that once #102 is merged. From the most recent
commits it looks like k8s networking may evolve further in the next major
release (0.8x).

--sent from my phone
On Jan 2, 2015 3:53 PM, "Timothy St. Clair" notifications@github.com
wrote:

@jdef https://github.com/jdef I'm not following the "IP-per-service"?

Latest word on the Docker front was that their networking plugins were due
out in ~1-2 Months which will likely ripple all the way through.

—
Reply to this email directly or view it on GitHub
#5 (comment)
.

[timothysc]

@jdef Sadly there are 1/2 a dozen networking proposals open, and Docker follows the, "it will be open source once we chuck it over the fence" mantra. I'm not entirely certain what the final secret sauce will contain...

[jdef]

ipv6 has landed in Docker

• Adding IPv6 network support to docker daemon moby/moby#8947
• Support and/or exploit ipv6 kubernetes/kubernetes#1443

[timothysc]

Also upstream networking proposal for interface:
moby/moby#9983

[jdef]

k8s networking plugins: kubernetes/kubernetes#5069

[jdef]

#785 fixes some problems when trying to run k8s-mesos w/ native k8s networking (including overlay solutions)