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

Weave 1.9.5
Compare
Choose a tag to compare
@bboreham bboreham released this 04 May 11:01
· 1536 commits to master since this release
v1.9.5
041b6fe

Bug fixes and minor improvements

  • Improve log messages generated if "hairpin" conditions are detected, to make clear which kind is likely to cause problems #2808/#2926
  • Filter out IPv6 peer addresses from Kubernetes; Weave Net currently only supports IPv4 #2904/#2912
  • Fix rare crash during initialization of weave-kube #2893/#2892
  • Include overlay and encryption modes in checkpoint reports, in case this is relevant to a version upgrade #2771/#2907

Build and Testing

  • Ensure CI build can run gcloud tools #2887
  • Prevent kubeadm from upgrading Kubernetes if we are trying to test an older version #2886
  • Upgrade build scripts to support Kubernetes 1.6 #2880

Full list of changes.

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.5 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.0 and 1.6.1 (#44041) means that Weave Net will not pick up existing pod IP addresses on a restart. We recommend you upgrade to Kubernetes 1.6.2, but if you are unable to do so then please reboot instead of individually deleting the Weave Net pods.

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:
keontang
mikebryant
nhlfr
roberth
tobowers

Assets 5
Loading