levaliciousandClaude Opus 5.5 9bc3415111
images / images (push) Successful in 14m46s
lb: LoadBalancer Services from addresses nodes hold, client address kept
A Service of type LoadBalancer with loadBalancerClass
reweave.levk.dev/node-address names its address in spec.loadBalancerIP.
Each node's weave-npc publishes the IPv4 addresses on its host interfaces
and its weave bridge (Node annotations reweave.levk.dev/addresses and
reweave.levk.dev/weave). The one node that holds a Service's address is
its holder: it alone writes status.loadBalancer (ipMode Proxy, so
kube-proxy installs nothing for the address) and DNATs the address's ports
to ready endpoints (EndpointSlices), without SNAT, from nat PREROUTING
ahead of kube-proxy. Every other node marks the connections the holder
forwards to its pods (new, from the holder's bridge MAC, from outside the
pod network) and routes their replies back to the holder's bridge through
a per-holder policy rule and table, so the holder's conntrack undoes the
DNAT and the reply leaves from the address the client connected to.

Fail closed: an address no node holds, or that several nodes hold, is
served by no node, and its status is cleared (by its holder, or by the
first node by name if none holds it). Compute is the policy as a pure
function; Datapath replaces exactly the chains it owns with
iptables-restore --noflush and keeps its rules and tables exact.

weave-npc runs it unless --lb=false; the ClusterRole gains services
(watch), services/status (patch), endpointslices (watch), nodes (patch).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01UHXzGrsxfkGk8LmwrBbHNZ
2026-10-13 12:45:54 -04:00
2020-07-31 16:28:52 +00:00
2024-07-19 08:54:16 +05:30
2023-03-27 23:40:04 +05:30
2021-07-13 16:18:37 +02:00
2018-04-27 14:34:47 +01:00
2024-12-22 20:54:31 +05:30
…
2024-07-19 08:54:16 +05:30
2018-08-14 12:32:57 +02:00

Weave Net

This repository contains a fork of Weave Net, the first product developed by Weaveworks. Since Weaveworks has shut down, this repo aims to continue maintaining Weave Net, and to publish releases regularly.

Go Report Card Docker Pulls GitHub release (latest by date) Unique CVE count in all images

The history of the fork can be found in HISTORY.md.

Using Weave Net on Kubernetes

On a newly created Kubernetes cluster, the Weave Net CNI pluging can be installed by running the following command:

kubectl apply -f https://reweave.azurewebsites.net/k8s/v1.29/net.yaml

Replace v1.29 with the version on Kubernetes on your cluster.

That endpoint is provided by the companion project weave-endpoint.

Using Weave Net in other ways

Please refer to the documentation.

Building Weave Net

Details can be found here.

Documentation status

The public documentation that used to exist in the site directory has been moved to the original/site directory. A new website directory has been created, and populated with the content of the original/site directory, rearranged and reformatted for being built with Jekyll and published to the GitHub pages site https://rajch.github.io/weave.

The documentation will now be maintained and published from the website directory exclusively.

S
Description
Weave Net fork (from rajch/weave)
Readme
36 MiB
0 Stars 1 Watchers 0 Forks
Languages
Go 73.7%
Shell 21.8%
Makefile 2.4%
Dockerfile 1.5%
Ruby 0.3%
Other 0.3%