Merge branch '2.0'

This commit is contained in:
Bryan Boreham committed 2017-10-11 10:49:13 +00:00
commit 0791ce8ab0
4 files changed
+21 -3

No files matched your search

+18
View File
@@ -1,3 +1,21 @@
## Release 2.0.5
Bug fixes
* Fix /etc/hosts inside containers so the container's name resolves to
its Weave Net address #3136,#3138
* New weave-kube config for Kubernetes 1.7 and 1.8 which resolves an
intermittent conflict with kube-proxy that could break Weave Net
until reboot #2998,#3134
* Remove persistence file in `weave reset` when using Docker plugin V2 #3103,#3114
Build and test
* Some trivial changes to placate go-lint #3137
[Full list of changes](https://github.com/weaveworks/weave/milestone/63?closed=1).
## Release 2.0.4 ## Release 2.0.4
Bug fixes Bug fixes
+1 -1
View File
@@ -39,7 +39,7 @@ You do not have to keep track of and specify the addresses
of other dynamic peers in `$PEERS` - they will discover and connect to of other dynamic peers in `$PEERS` - they will discover and connect to
each other via the fixed cluster. each other via the fixed cluster.
>>**Note:** The use of `--ipalloc-init=observer` prevents dynamic peers from >**Note:** The use of `--ipalloc-init=observer` prevents dynamic peers from
coming to a consensus on their own - this is important to stop a coming to a consensus on their own - this is important to stop a
clique forming amongst a group of dynamically added peers if they clique forming amongst a group of dynamically added peers if they
become partitioned from the fixed cluster after having learned about become partitioned from the fixed cluster after having learned about
+1 -1
View File
@@ -99,7 +99,7 @@ To minimize downtime while the new script is pulling the new container images:
* Start the new Weave Net with `weave launch <existing peer list>` (or * Start the new Weave Net with `weave launch <existing peer list>` (or
`systemctl start weave` if you're using a systemd unit file) `systemctl start weave` if you're using a systemd unit file)
>>**Note:** Always check the Release Notes for specific versions in case >**Note:** Always check the Release Notes for specific versions in case
there are any special caveats or deviations from the standard there are any special caveats or deviations from the standard
procedure. procedure.
@@ -42,7 +42,7 @@ Then on _any_ peer run the following to force consensus:
weave prime weave prime
>>**Note:** You can run this safely on more than one or >**Note:** You can run this safely on more than one or
even all peers, but it's only strictly necessary to run it on one of even all peers, but it's only strictly necessary to run it on one of
them. them.