Simple, resilient multi-host containers networking and more.
Switch branches/tags
Clone or download
Latest commit 1b01da4 Oct 18, 2018
Failed to load latest commit information.
.circleci Fix CircleCI parse error Aug 10, 2018
.github Simplified May 31, 2017
api Code to reclaim IP address space from removed peers Nov 14, 2017
bin SRCDIR removed from this step Aug 10, 2018
build Fix golint path - it moved upstream Oct 16, 2018
common Update to match upstream changes Apr 27, 2018
db Ensure boltDB pathname is constructed uniformly Apr 11, 2017
docs Fix to use 10-weave.conflist instead of 10-weave.conf as CNI config f… Aug 31, 2018
ipam ipam: Do not deref nil in GET /ipinfo/tracker if tracker doesn't exist Sep 21, 2018
nameserver Move canonicalisation and checking of DNS entries into nameserver Apr 17, 2017
net Merge pull request #3388 from myENA/feature/skip-nat-via-weave-expose Sep 10, 2018
npc dont maintain weave-local-pods ipset on pod add/delete/update Oct 16, 2018
plugin 3206: Protect against CNI plugin being called with the host namespace Jul 16, 2018
prog Merge pull request #3423 from weaveworks/issue-3344 Oct 17, 2018
proxy Pass the WeaveDNS Domain into the proxy Jan 29, 2018
router addressing review comment. keep forwarder running forever even on hea… Oct 5, 2018
site Merge branch '2.4' Sep 6, 2018
test integration test for HostPort support Sep 5, 2018
testing Fake kubernetes API which implements optimistic locking Sep 12, 2018
tools @ ca69607 Update build-tools to include the defunct process fix Jan 29, 2018
vendor Bump go-odp dependency Oct 17, 2018
.ackrc Add .ackrc which excludes vendor/ and .pkg/ May 17, 2016
.gitignore updates to address comments by @bboreham Aug 31, 2018
.gitmodules Remove vendor submodules Apr 27, 2018
.lintignore Run coverage analysis in separate step, and save results Jul 30, 2018
.ruby-version Put the Ruby version back to 2.3.0 until we update Netlify Jun 16, 2017 Add release v2.4.1 Sep 13, 2018 Add vendor instructions Apr 27, 2018
COPYING.LGPL-3 license: document vendored code which is under LGPL3 and MPL-2.0 Aug 14, 2018
DEPENDENCIES Bump to Kubernetes 1.11 Jun 28, 2018
Gopkg.lock Bump go-odp dependency Oct 17, 2018
Gopkg.toml Use k8s/client-go v8.0.0 Aug 3, 2018
LICENSE Bump license copyright year to 2017 (#3132) Oct 3, 2017
Makefile Tag build image with current git commit Jul 30, 2018
NOTICE update year in copyright notices Jan 5, 2016 update links in readme anchors Jul 20, 2017 make markdownlint happier Aug 14, 2018
Vagrantfile Add DEPENDENCIES file and source Vagrant and tests versions from it. Feb 13, 2017 Add pointing to CNCF CoC May 2, 2017
vagrant-common.rb change golang version Mar 5, 2018
weave Merge pull request #3388 from myENA/feature/skip-nat-via-weave-expose Sep 10, 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