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

Weave 1.9.6
Compare
Choose a tag to compare
@bboreham bboreham released this 30 May 16:50
· 1494 commits to master since this release
v1.9.6
afb0d5b

Bug fixes and minor improvements

  • Ensure that Kubernetes pods can contact a service implemented within the same pod, by turning on "hairpin mode". This is required because of a quiet change between Kubernetes 1.5 and 1.6. #2993
  • Network Policy Controller (weave-npc) now checks local addresses only, so it doesn't interfere with cross-cluster traffic. It should be more efficient too #2622,#2973,#2979
  • Stop reporting back to Kubernetes any issues encountered when deleting a pod's network interface. This is required because of a quiet change between Kubernetes 1.5 and 1.6. #2921,#2928
  • Fixed an issue whereby weave-npc couldn't start because one ipset was referring to another one and could not be destroyed #2915,#2949
  • Improved the code which checks whether the kernel supports ipset #2934,#2935
  • weave-npc now creates ipsets with only valid xml characters in the name #2958,#2959

Build and Testing

  • In build container use cross-compilers from debian package repository, so they match other components #2940
  • Pin the version of the linting tool shfmt so the set of things it checks is stable #2987
  • Fix lint error in script that runs smoke-tests #2962
  • Moved website publishing from Wordpress to Netlify #2986

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.6 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

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:
@deitch
@mikebryant
@stuart-warren

Assets 5
Loading