-
Notifications
You must be signed in to change notification settings - Fork 92
Networking TBD. #5
Comments
Why not use openvswitch and gre tunnels? |
Here is a broad overview. |
related, some recent activity in k8s for service networking, using an IP-per-service model:
will (minimally) require sync'ing our godeps to the latest k8s (probably a good amount of work here) |
related docker work to eliminate userland proxies: |
Docker is proposing native ovs integration. |
Yeah, I've been tracking. Many of the new proposals could change more then networking. |
|
FWIW, it's my understanding that flannel is a v1 get the ball rolling solution with a plan for replacement. |
IP-per-service will land with #102 |
@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. |
I'll have to catch up with docker networking. K8s introduced service --sent from my phone
|
@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... |
Also upstream networking proposal for interface: |
k8s networking plugins: kubernetes/kubernetes#5069 |
#785 fixes some problems when trying to run k8s-mesos w/ native k8s networking (including overlay solutions) |
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.
The text was updated successfully, but these errors were encountered: