From 9232ad819165a48639452b2542bc311b88c31a0c Mon Sep 17 00:00:00 2001 From: MattTheCuber Date: Tue, 28 Dec 2021 19:23:22 -0500 Subject: [PATCH] typo in troubleshooting documentation --- Documentation/troubleshooting.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Documentation/troubleshooting.md b/Documentation/troubleshooting.md index 435b680336..a28411f828 100644 --- a/Documentation/troubleshooting.md +++ b/Documentation/troubleshooting.md @@ -22,7 +22,7 @@ Flannel uses the `klog` library but only supports logging to stderr. The severit When running under systemd (e.g. on CoreOS Container Linux) the logs can be viewed with `journalctl -u flanneld` -When flannel is running as a pod on Kubernetes, the logs can be viewed with `kubectl logs --namespace kube-system -c kube-flannel`. You can find the pod IDs with `kubectl get po --namespace kube-system -l app=flannel` +When flannel is running as a pod on Kubernetes, the logs can be viewed with `kubectl logs --namespace kube-system -c kube-flannel`. You can find the pod IDs with `kubectl get pod --namespace kube-system -l app=flannel` ## Interface selection and the public IP. Most backends require that each node has a unique "public IP" address. This address is chosen when flannel starts. Because leases are tied to the public address, if the address changes, flannel must be restarted.