Weave 1.9.8
Release 1.9.8
Bug fixes and minor improvements
- Fix weave-npc blocking NodePort and any other non-local access #3011,#3014
- Fix bug where IPAM would duplicate a fixed IP address assigned via Docker plugin #3003,#3010
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.8 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 from an earlier version to version 1.6
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)
Although Kubernetes 1.6 now supports rolling upgrades of daemonsets, we have not tested this or changed the configuration for it, so we still recommend you perform the procedure manually - see https://weave.works/docs/net/latest/kube-addon/ for details.