Skip to content
This repository was archived by the owner on Jun 20, 2024. It is now read-only.

Weave Net 1.9.4
Compare
Choose a tag to compare
@bboreham bboreham released this 21 Mar 15:37
· 1574 commits to master since this release
v1.9.4
178cf85

Bug fixes and minor improvements

  • Support Kubernetes 1.6 - a new DaemonSet is required (see below for upgrading) #2777,#2801
  • Support Kubernetes 1.6 by allowing CNI callers to send a network-delete request for a container that is not running or has never been attached to the network #2850
  • Leave non-weave ipsets alone in Network Policy Controller (e.g. when running Weave Net alonside keepalived-vip) #2751,#2846
  • Fix various small issues revealed by 'staticcheck' tool #2843,#2857
  • Avoid leaving 'defunct' processes when weave-kube container restarts #2836,#2845
  • When using the CNI plugin with a non-standard network configuration file, the weave bridge could get the same IP as a container, if 'weave expose' hadn't run at that point #2839,#2856

Build and Testing

  • Check that no defunct processes remain after each test #2852
  • Update build and test scripts to work with Kubernetes 1.6 beta #2851

Installation and Upgrading of Weave Net

Follow the installation instructions to install this latest release of weave.

When upgrading from a version earlier than 1.9.0, if your host's network interface has a limit on packet size (the "MTU") smaller than 1496 bytes, you should reboot after upgrading to ensure encrypted fast datapath can work. For instance this applies to Google Cloud Platform, but is not necessary on AWS.

Weave Net 1.9.4 is fully compatible with all previous versions back to 1.1.0, so it is possible to upgrade clusters incrementally and run mixed versions.

Upgrading Kubernetes to version 1.6

Note a bug in Kubernetes 1.6 (#44041) means that Weave Net will not pick up existing pod IP addresses on a restart. Until this is fixed we recommend you reboot instead of individually deleting the Weave Net pod.

In version 1.6, Kubernetes has increased security, so we need to create a special service account to run Weave Net. This is done in the file weave-daemonset-k8s-1.6.yaml attached to the release.

Also, the toleration required to let Weave Net run on master nodes has moved from an annotation to a field on the DaemonSet spec object.

The command to apply this new configuration via short URL is:

kubectl apply -f https://git.io/weave-kube-1.6

If you have edited the Weave Net DaemonSet from a previous release, you will need to re-make your changes against the new version.

Upgrading the Weave Net Kubernetes addon (weave-kube)

Kubernetes does not currently support rolling upgrades of daemon sets, so you will need to perform the procedure manually - see https://weave.works/docs/net/latest/kube-addon/ for details.

External Contributors

Thanks to the following who contributed changes during this release:
stephan2012

Assets 5
Loading