From fc199d0df556f2ad1f2847547abc81b0eb3c909b Mon Sep 17 00:00:00 2001 From: Daniel Holbach Date: Fri, 2 Aug 2019 09:53:07 +0200 Subject: [PATCH] Answer how Weave Net works Actually Bryan answered it, when a reader of our website asked. Signed-off-by: Daniel Holbach --- site/overview.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/site/overview.md b/site/overview.md index 850a030e..fca94748 100644 --- a/site/overview.md +++ b/site/overview.md @@ -9,6 +9,9 @@ Weave Net creates a virtual network that connects Docker containers across multi Services provided by application containers on the weave network can be exposed to the outside world, regardless of where they are running. Similarly, existing internal systems can be opened to accept connections from application containers irrespective of their location. +### How does it work? + +Weave Net creates a new Layer 2 network using Linux kernel features; one daemon sets up that network and manages routing between machines and there are various ways to attach to that network (e.g. a CNI plugin which runs as a separate process). Also one more daemon if you are using Kubernetes Network Policy. ## Why Weave?