whentimeslows/website
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Update debug-service.md (#12599)

Browse Source 
use smaller case `v` for adjusting logging level
This commit is contained in:
Tomas Kral
2019-02-13 11:15:06 +01:00
committed by Kubernetes Prow Robot
parent 8c637cee9e
commit 32211de0f5
1 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
content/en/docs/tasks/debug-application-cluster/debug-service.md
+2 -2
View File
@@ -489,7 +489,7 @@ u@node$ iptables-save | grep hostnames
There should be 2 rules for each port on your `Service` (just one in this There should be 2 rules for each port on your `Service` (just one in this
example) - a "KUBE-PORTALS-CONTAINER" and a "KUBE-PORTALS-HOST". If you do example) - a "KUBE-PORTALS-CONTAINER" and a "KUBE-PORTALS-HOST". If you do
not see these, try restarting `kube-proxy` with the `-V` flag set to 4, and not see these, try restarting `kube-proxy` with the `-v` flag set to 4, and
then look at the logs again. then look at the logs again.
Almost nobody should be using the "userspace" mode any more, so we won't spend Almost nobody should be using the "userspace" mode any more, so we won't spend
@@ -559,7 +559,7 @@ If this still fails, look at the `kube-proxy` logs for specific lines like:
Setting endpoints for default/hostnames:default to [10.244.0.5:9376 10.244.0.6:9376 10.244.0.7:9376] Setting endpoints for default/hostnames:default to [10.244.0.5:9376 10.244.0.6:9376 10.244.0.7:9376]
``` ```
If you don't see those, try restarting `kube-proxy` with the `-V` flag set to 4, and If you don't see those, try restarting `kube-proxy` with the `-v` flag set to 4, and
then look at the logs again. then look at the logs again.
### A Pod cannot reach itself via Service IP ### A Pod cannot reach itself via Service IP