Merge remote-tracking branch 'origin/2.3'
This commit is contained in:
commit
6dce685105
9 files changed
+99
-19
No files matched your search
@@ -307,6 +307,11 @@ UDP connection from 10.32.0.7:56648 to 10.32.0.11:80 blocked by Weave NPC.
|
||||
pods can talk.
|
||||
- If you do set the `--cluster-cidr` option on kube-proxy, make sure
|
||||
it matches the `IPALLOC_RANGE` given to Weave Net (see below)
|
||||
- IP forwarding must be enabled on each node, in order for pods to
|
||||
access Kubernetes services or other IP addresses on another
|
||||
network. Check this with `sysctl net.ipv4.ip_forward`; the result
|
||||
should be `1`. (Be aware that there can be security implications of
|
||||
enabling IP forwarding)
|
||||
|
||||
## <a name="configuration-options"></a> Changing Configuration Options
|
||||
|
||||
|
||||
@@ -67,3 +67,18 @@ Columns are as follows:
|
||||
partition, it may be because the peer has failed and needs to be
|
||||
removed administratively - see [Starting, Stopping and Removing
|
||||
Peers](/site/tasks/ipam/stop-remove-peers-ipam.md) for more details.
|
||||
|
||||
|
||||
### <a name="seeded-different-peers"></a>Seeded by Different Peers
|
||||
|
||||
If you see the message: `IP allocation was seeded by different peers`,
|
||||
this means that some Weave Net peers were initialized into one cluster
|
||||
and some into another cluster; Weave Net cannot operate in this state.
|
||||
|
||||
To recover, you need to eliminate the IPAM data from the affected
|
||||
nodes and restart. If you installed via the Kubernetes Addon, this
|
||||
data will be in a file under `/var/lib/weave` on the node - delete
|
||||
this file and restart the node.
|
||||
|
||||
For other installations, run `weave reset` and restart. Any existing
|
||||
connections to containers will be lost.
|
||||
@@ -157,6 +157,9 @@ The columns are as follows:
|
||||
the encryption mode, data transport method, remote peer name and
|
||||
nickname for pending and established connections, mtu if known
|
||||
|
||||
Specific error messages:
|
||||
* `IP allocation was seeded by different peers` - [more details here](/site/ipam/troubleshooting-ipam.md#seeded-different-peers)
|
||||
|
||||
### <a name="weave-status-peers"></a>List Peers
|
||||
|
||||
Detailed information on peers can be obtained with `weave status
|
||||
@@ -329,5 +332,6 @@ and the container image versions as git hashes.
|
||||
|
||||
**See Also**
|
||||
|
||||
* [Troubleshooting the Kubernetes Addon](/site/kubernetes/kube-addon/#troubleshooting)
|
||||
* [Troubleshooting IPAM](/site/tasks/ipam/troubleshooting-ipam.md)
|
||||
* [Troubleshooting the Proxy](/site/tasks/weave-docker-api/using-proxy.md)
|
||||
Reference in new issue
Block a user