Skip to content

Commit bc94bad

Browse files
committed
remove conntrack ref from debug/debug-application/debug-service
Signed-off-by: Daman Arora <[email protected]>
1 parent 7116eef commit bc94bad

File tree

1 file changed

+0
-7
lines changed

1 file changed

+0
-7
lines changed

content/en/docs/tasks/debug/debug-application/debug-service.md

Lines changed: 0 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -539,13 +539,6 @@ I1027 22:14:54.040223 5063 proxier.go:294] Adding new service "kube-system/ku
539539
If you see error messages about not being able to contact the master, you
540540
should double-check your Node configuration and installation steps.
541541

542-
One of the possible reasons that `kube-proxy` cannot run correctly is that the
543-
required `conntrack` binary cannot be found. This may happen on some Linux
544-
systems, depending on how you are installing the cluster, for example, you are
545-
installing Kubernetes from scratch. If this is the case, you need to manually
546-
install the `conntrack` package (e.g. `sudo apt install conntrack` on Ubuntu)
547-
and then retry.
548-
549542
Kube-proxy can run in one of a few modes. In the log listed above, the
550543
line `Using iptables Proxier` indicates that kube-proxy is running in
551544
"iptables" mode. The most common other mode is "ipvs".

0 commit comments

Comments
 (0)