Simple, resilient multi-host containers networking and more.
Go Shell Makefile Other
Switch branches/tags
Clone or download
bboreham Merge pull request #3346 from murali-reddy/issue-3206
3206: Protect against CNI plugin being called with the host namespace
Latest commit b8ce722 Jul 19, 2018
Failed to load latest commit information.
.github Simplified May 31, 2017
api Code to reclaim IP address space from removed peers Nov 14, 2017
bin Fix release script for plugin latest_release Nov 27, 2017
build Use go1.10.1 for building Apr 9, 2018
common Update to match upstream changes Apr 27, 2018
db Ensure boltDB pathname is constructed uniformly Apr 11, 2017
docs Merge pull request #3277 from weaveworks/ml-release-docs May 23, 2018
ipam Export tracker.RemoveCommon and tracker.Merge Jun 4, 2018
nameserver Move canonicalisation and checking of DNS entries into nameserver Apr 17, 2017
net Merge remote-tracking branch 'origin/2.3' Jun 11, 2018
npc Move npc/ipset package to net/ipset Jun 4, 2018
plugin 3206: Protect against CNI plugin being called with the host namespace Jul 16, 2018
prog Add permissions to set node status Jun 21, 2018
proxy Pass the WeaveDNS Domain into the proxy Jan 29, 2018
router Demote messages about MAC discovery and expiry to DEBUG level Dec 18, 2017
site Merge branch '2.3' Jul 17, 2018
test Add --force flag to kubeadm reset Jun 28, 2018
testing don't panic when TestMain is invoked as a regular test Jun 25, 2017
tools @ ca69607 Update build-tools to include the defunct process fix Jan 29, 2018
vendor Copy dependencies into vendor dir, using dep Apr 27, 2018
.ackrc Add .ackrc which excludes vendor/ and .pkg/ May 17, 2016
.gitignore Merge pull request #3307 from weaveworks/set-kube-netstatus Jun 11, 2018
.gitmodules Remove vendor submodules Apr 27, 2018
.lintignore Revert "Disable temporary 840 smoke tests" Apr 6, 2017
.ruby-version Put the Ruby version back to 2.3.0 until we update Netlify Jun 16, 2017 Add release v2.3.0 Apr 9, 2018 Add vendor instructions Apr 27, 2018
CONTRIBUTORS initial commit Aug 18, 2014
DEPENDENCIES Bump to Kubernetes 1.11 Jun 28, 2018
Gopkg.lock Copy dependencies into vendor dir, using dep Apr 27, 2018
Gopkg.toml Copy dependencies into vendor dir, using dep Apr 27, 2018
LICENSE Bump license copyright year to 2017 (#3132) Oct 3, 2017
Makefile Fix manifest-tool cmd in Makefile Jun 12, 2018
NOTICE update year in copyright notices Jan 5, 2016 update links in readme anchors Jul 20, 2017
Vagrantfile Add DEPENDENCIES file and source Vagrant and tests versions from it. Feb 13, 2017
circle.yml Add k8s integration test case for preserving client IP addr Jun 4, 2018 Add pointing to CNCF CoC May 2, 2017
vagrant-common.rb change golang version Mar 5, 2018
weave Issue #3337: fix upgrade_cni_plugin Jul 9, 2018

Weave Net - Weaving Containers into Applications

Integration Tests Coverage Status Go Report Card Docker Pulls

About Weaveworks

Weaveworks is the company that delivers the most productive way for developers to connect, observe and control Docker containers.

This repository contains Weave Net, the first product developed by Weaveworks, and with over 8 million downloads to date, enables you to get started with Docker clusters and portable apps in a fraction of the time compared with other solutions.

Weave Cloud:

Weave Cloud is software-as-a-service that simplifies deployment, monitoring and management for containers and microservices. It extends and complements popular orchestrators, and enables developers and DevOps to realize faster deployments, insightful monitoring, visualization and networking.

Weave Cloud is built using these Open Source projects: Weave Scope, a powerful container visualization tool that automatically maps Docker containers and their interactions, Weave Cortex, a horizontally-scalable version of Prometheus, and Weave Flux, a continuous deployment tool that works with Kubernetes.

Weave Net

Weave Net creates a virtual network that connects Docker containers across multiple hosts and enables their automatic discovery. With Weave Net, portable microservices-based applications consisting of multiple containers can run anywhere: on one host, multiple hosts or even across cloud providers and data centers. Applications use the network just as if the containers were all plugged into the same network switch, without having to configure port mappings, ambassadors or links.

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.

Getting help

If you have any questions about, feedback for or a problem with Weave Net:

Your feedback is always welcome!

Further Information