Review feedback

This commit is contained in:
Bryan Boreham committed 2018-07-17 10:24:26 +01:00
1 parent bb1a373272
commit ac9f47783c
1 file changed
+13 -8
+13 -8
View File
@@ -15,6 +15,7 @@ The following topics are discussed:
* [Pod Network](#pod-network)
* [Network Policy](#npc)
* [Troubleshooting](#troubleshooting)
* [Reading the logs](#logs)
* [Troubleshooting Blocked Connections](#blocked-connections)
* [Things to watch out for](#key-points)
* [Changing Configuration Options](#configuration-options)
@@ -186,10 +187,11 @@ definition](https://v1-7.docs.kubernetes.io/docs/api-reference/v1.7/#networkpoli
## <a name="troubleshooting"></a> Troubleshooting
The first thing to check is whether the Weave Net software is up and
running. The `kubectl apply` command you use to install only
The first thing to check is whether Weave Net is up and
running. The `kubectl apply` command you used to install it only
_requests_ that it be downloaded and started; if anything goes wrong
at startup the details will only be visible in the logs of the container(s).
at startup, those details will only be visible in the [logs](#logs) of
the container(s).
To check what is running:
@@ -202,17 +204,20 @@ weave-net-m4x1b 2/2 Running 0 1d
```
You should see one line for each node in your cluster; each line
should have STATUS "Running", and READY should be 2 out of 2.
should have STATUS "Running", and READY should be 2 out of 2. If you
see a STATUS like "Error" or "CrashLoopBackoff", look in the logs of
the container with that status.
If you see a STATUS like "Error" or "CrashLoopBackoff", look in the
logs. Pick one of the pods with that status from the list and ask for
the logs like this:
### <a name="logs"></a> Reading the logs
Pick one of the pods from the list output by `kubectl get pods` and
ask for the logs like this:
```
$ kubectl logs -n kube-system weave-net-1jkl6 weave
```
You can pipe the output into a file for easier viewing, especially if
For easier viewing, pipe the output into a file , especially if
it is long.
Many Kubernetes network issues occur at a higher level than Weave Net.