This release adds support for Kubernetes `hostPort` mapping and the
`ipBlock` NetworkPolicy feature, plus many other improvements.
Release notes https://github.com/weaveworks/weave/releases/tag/v2.5.0
Signed-off-by: Bryan Boreham <bjboreham@gmail.com>
- New manifest for k8s 1.8.0 due to FileOrCreate mount type.
- RBAC for updating NetworkUnavailable node status.
- Dropped support for legacy NetworkPolicy (k8s pre-1.7).
Full changelog: https://github.com/weaveworks/weave/releases/tag/v2.4.0
Weave limits the number of connections between peers and the default is 30.
As described here: ce9c5162bd/site/kubernetes/kube-addon.md
Setting the CONN_LIMIT environment variable controls this setting. Adding a field in the
WeaveNetworkingSpec and adding the env var to the associated templates lets users
have clusters larger than 30 nodes and still use weave's peer discovery
The weave authors have indicated that 100 is not an unreasonable setting.
https://github.com/weaveworks/weave/issues/1621#issuecomment-152713060
* Limit each CNI provider to 100m
* Remove CPU limits - they cause serious problems
(https://github.com/kubernetes/kubernetes/issues/51135), but this also
makes the CPU allocation less problematic.
* Bump versions and start introducing the `-kops.1` suffix preemptively.
* Upgrade flannel to 0.9.0 as it fixes a lot.
including a Weave Net template for Kubernetes 1.7 and above which adds
a volume-mount for the iptables lock file, which avoids collisions
between Weave components and kube-proxy that would result in a
half-configured Weave network.
This is only for version 1.7 and above because it requires the change
in https://github.com/kubernetes/kubernetes/issues/47212
Otherwise the kops 1.5 -> kops 1.6 upgrade was failing with:
The DaemonSet "weave-net" is invalid: spec.template.metadata.labels:
Invalid value: {"name":"weave-net"}: `selector` does not match template
`labels`
Fix#2345