diff --git a/linkerd.io/content/2-edge/reference/iptables.md b/linkerd.io/content/2-edge/reference/iptables.md index 67a7ea89de..c207bd01d4 100644 --- a/linkerd.io/content/2-edge/reference/iptables.md +++ b/linkerd.io/content/2-edge/reference/iptables.md @@ -164,7 +164,7 @@ Alternatively, if you want to inspect the iptables rules created for a pod, you can retrieve them through the following command: ```bash -$ kubectl -n logs linkerd-init +$ kubectl -n logs linkerd-init # where is the name of the pod # you want to see the iptables rules for ``` diff --git a/linkerd.io/content/2-edge/tasks/troubleshooting.md b/linkerd.io/content/2-edge/tasks/troubleshooting.md index baaa71e206..4131ad328f 100644 --- a/linkerd.io/content/2-edge/tasks/troubleshooting.md +++ b/linkerd.io/content/2-edge/tasks/troubleshooting.md @@ -1272,7 +1272,7 @@ Example failure: Ensure that all the CNI pods are running: ```bash -$ kubectl get po -n linkerd-cn +$ kubectl get po -n linkerd-cni NAME READY STATUS RESTARTS AGE linkerd-cni-rzp2q 1/1 Running 0 9m20s linkerd-cni-mf564 1/1 Running 0 9m22s diff --git a/linkerd.io/content/2.10/tasks/troubleshooting.md b/linkerd.io/content/2.10/tasks/troubleshooting.md index ee27242c04..7c54ec5557 100644 --- a/linkerd.io/content/2.10/tasks/troubleshooting.md +++ b/linkerd.io/content/2.10/tasks/troubleshooting.md @@ -1324,7 +1324,7 @@ Example failure: Ensure that all the CNI pods are running: ```bash -$ kubectl get po -n linkerd-cn +$ kubectl get po -n linkerd-cni NAME READY STATUS RESTARTS AGE linkerd-cni-rzp2q 1/1 Running 0 9m20s linkerd-cni-mf564 1/1 Running 0 9m22s diff --git a/linkerd.io/content/2.11/reference/iptables.md b/linkerd.io/content/2.11/reference/iptables.md index 67a7ea89de..c207bd01d4 100644 --- a/linkerd.io/content/2.11/reference/iptables.md +++ b/linkerd.io/content/2.11/reference/iptables.md @@ -164,7 +164,7 @@ Alternatively, if you want to inspect the iptables rules created for a pod, you can retrieve them through the following command: ```bash -$ kubectl -n logs linkerd-init +$ kubectl -n logs linkerd-init # where is the name of the pod # you want to see the iptables rules for ``` diff --git a/linkerd.io/content/2.11/tasks/troubleshooting.md b/linkerd.io/content/2.11/tasks/troubleshooting.md index 3a988974a6..b69bef1d09 100644 --- a/linkerd.io/content/2.11/tasks/troubleshooting.md +++ b/linkerd.io/content/2.11/tasks/troubleshooting.md @@ -1471,7 +1471,7 @@ Example failure: Ensure that all the CNI pods are running: ```bash -$ kubectl get po -n linkerd-cn +$ kubectl get po -n linkerd-cni NAME READY STATUS RESTARTS AGE linkerd-cni-rzp2q 1/1 Running 0 9m20s linkerd-cni-mf564 1/1 Running 0 9m22s diff --git a/linkerd.io/content/2.12/reference/iptables.md b/linkerd.io/content/2.12/reference/iptables.md index 67a7ea89de..c207bd01d4 100644 --- a/linkerd.io/content/2.12/reference/iptables.md +++ b/linkerd.io/content/2.12/reference/iptables.md @@ -164,7 +164,7 @@ Alternatively, if you want to inspect the iptables rules created for a pod, you can retrieve them through the following command: ```bash -$ kubectl -n logs linkerd-init +$ kubectl -n logs linkerd-init # where is the name of the pod # you want to see the iptables rules for ``` diff --git a/linkerd.io/content/2.12/tasks/troubleshooting.md b/linkerd.io/content/2.12/tasks/troubleshooting.md index 7ec6896a2d..03ff0fd8d6 100644 --- a/linkerd.io/content/2.12/tasks/troubleshooting.md +++ b/linkerd.io/content/2.12/tasks/troubleshooting.md @@ -1243,7 +1243,7 @@ Example failure: Ensure that all the CNI pods are running: ```bash -$ kubectl get po -n linkerd-cn +$ kubectl get po -n linkerd-cni NAME READY STATUS RESTARTS AGE linkerd-cni-rzp2q 1/1 Running 0 9m20s linkerd-cni-mf564 1/1 Running 0 9m22s diff --git a/linkerd.io/content/2.13/reference/iptables.md b/linkerd.io/content/2.13/reference/iptables.md index 67a7ea89de..c207bd01d4 100644 --- a/linkerd.io/content/2.13/reference/iptables.md +++ b/linkerd.io/content/2.13/reference/iptables.md @@ -164,7 +164,7 @@ Alternatively, if you want to inspect the iptables rules created for a pod, you can retrieve them through the following command: ```bash -$ kubectl -n logs linkerd-init +$ kubectl -n logs linkerd-init # where is the name of the pod # you want to see the iptables rules for ``` diff --git a/linkerd.io/content/2.13/tasks/troubleshooting.md b/linkerd.io/content/2.13/tasks/troubleshooting.md index 7ec6896a2d..03ff0fd8d6 100644 --- a/linkerd.io/content/2.13/tasks/troubleshooting.md +++ b/linkerd.io/content/2.13/tasks/troubleshooting.md @@ -1243,7 +1243,7 @@ Example failure: Ensure that all the CNI pods are running: ```bash -$ kubectl get po -n linkerd-cn +$ kubectl get po -n linkerd-cni NAME READY STATUS RESTARTS AGE linkerd-cni-rzp2q 1/1 Running 0 9m20s linkerd-cni-mf564 1/1 Running 0 9m22s diff --git a/linkerd.io/content/2.14/reference/iptables.md b/linkerd.io/content/2.14/reference/iptables.md index 67a7ea89de..c207bd01d4 100644 --- a/linkerd.io/content/2.14/reference/iptables.md +++ b/linkerd.io/content/2.14/reference/iptables.md @@ -164,7 +164,7 @@ Alternatively, if you want to inspect the iptables rules created for a pod, you can retrieve them through the following command: ```bash -$ kubectl -n logs linkerd-init +$ kubectl -n logs linkerd-init # where is the name of the pod # you want to see the iptables rules for ``` diff --git a/linkerd.io/content/2.14/tasks/troubleshooting.md b/linkerd.io/content/2.14/tasks/troubleshooting.md index 7ec6896a2d..03ff0fd8d6 100644 --- a/linkerd.io/content/2.14/tasks/troubleshooting.md +++ b/linkerd.io/content/2.14/tasks/troubleshooting.md @@ -1243,7 +1243,7 @@ Example failure: Ensure that all the CNI pods are running: ```bash -$ kubectl get po -n linkerd-cn +$ kubectl get po -n linkerd-cni NAME READY STATUS RESTARTS AGE linkerd-cni-rzp2q 1/1 Running 0 9m20s linkerd-cni-mf564 1/1 Running 0 9m22s diff --git a/linkerd.io/content/2.15/reference/iptables.md b/linkerd.io/content/2.15/reference/iptables.md index 67a7ea89de..c207bd01d4 100644 --- a/linkerd.io/content/2.15/reference/iptables.md +++ b/linkerd.io/content/2.15/reference/iptables.md @@ -164,7 +164,7 @@ Alternatively, if you want to inspect the iptables rules created for a pod, you can retrieve them through the following command: ```bash -$ kubectl -n logs linkerd-init +$ kubectl -n logs linkerd-init # where is the name of the pod # you want to see the iptables rules for ``` diff --git a/linkerd.io/content/2.15/tasks/troubleshooting.md b/linkerd.io/content/2.15/tasks/troubleshooting.md index bc58809cf8..3d7938a312 100644 --- a/linkerd.io/content/2.15/tasks/troubleshooting.md +++ b/linkerd.io/content/2.15/tasks/troubleshooting.md @@ -1258,7 +1258,7 @@ Example failure: Ensure that all the CNI pods are running: ```bash -$ kubectl get po -n linkerd-cn +$ kubectl get po -n linkerd-cni NAME READY STATUS RESTARTS AGE linkerd-cni-rzp2q 1/1 Running 0 9m20s linkerd-cni-mf564 1/1 Running 0 9m22s diff --git a/linkerd.io/content/2.16/reference/iptables.md b/linkerd.io/content/2.16/reference/iptables.md index 67a7ea89de..c207bd01d4 100644 --- a/linkerd.io/content/2.16/reference/iptables.md +++ b/linkerd.io/content/2.16/reference/iptables.md @@ -164,7 +164,7 @@ Alternatively, if you want to inspect the iptables rules created for a pod, you can retrieve them through the following command: ```bash -$ kubectl -n logs linkerd-init +$ kubectl -n logs linkerd-init # where is the name of the pod # you want to see the iptables rules for ``` diff --git a/linkerd.io/content/2.16/tasks/troubleshooting.md b/linkerd.io/content/2.16/tasks/troubleshooting.md index bc58809cf8..3d7938a312 100644 --- a/linkerd.io/content/2.16/tasks/troubleshooting.md +++ b/linkerd.io/content/2.16/tasks/troubleshooting.md @@ -1258,7 +1258,7 @@ Example failure: Ensure that all the CNI pods are running: ```bash -$ kubectl get po -n linkerd-cn +$ kubectl get po -n linkerd-cni NAME READY STATUS RESTARTS AGE linkerd-cni-rzp2q 1/1 Running 0 9m20s linkerd-cni-mf564 1/1 Running 0 9m22s diff --git a/linkerd.io/content/2.17/reference/iptables.md b/linkerd.io/content/2.17/reference/iptables.md index 67a7ea89de..c207bd01d4 100644 --- a/linkerd.io/content/2.17/reference/iptables.md +++ b/linkerd.io/content/2.17/reference/iptables.md @@ -164,7 +164,7 @@ Alternatively, if you want to inspect the iptables rules created for a pod, you can retrieve them through the following command: ```bash -$ kubectl -n logs linkerd-init +$ kubectl -n logs linkerd-init # where is the name of the pod # you want to see the iptables rules for ``` diff --git a/linkerd.io/content/2.17/tasks/troubleshooting.md b/linkerd.io/content/2.17/tasks/troubleshooting.md index a9efbc7ec1..37c341b2ef 100644 --- a/linkerd.io/content/2.17/tasks/troubleshooting.md +++ b/linkerd.io/content/2.17/tasks/troubleshooting.md @@ -1272,7 +1272,7 @@ Example failure: Ensure that all the CNI pods are running: ```bash -$ kubectl get po -n linkerd-cn +$ kubectl get po -n linkerd-cni NAME READY STATUS RESTARTS AGE linkerd-cni-rzp2q 1/1 Running 0 9m20s linkerd-cni-mf564 1/1 Running 0 9m22s diff --git a/linkerd.io/content/2.18/reference/iptables.md b/linkerd.io/content/2.18/reference/iptables.md index 67a7ea89de..c207bd01d4 100644 --- a/linkerd.io/content/2.18/reference/iptables.md +++ b/linkerd.io/content/2.18/reference/iptables.md @@ -164,7 +164,7 @@ Alternatively, if you want to inspect the iptables rules created for a pod, you can retrieve them through the following command: ```bash -$ kubectl -n logs linkerd-init +$ kubectl -n logs linkerd-init # where is the name of the pod # you want to see the iptables rules for ``` diff --git a/linkerd.io/content/2.18/tasks/troubleshooting.md b/linkerd.io/content/2.18/tasks/troubleshooting.md index ca2b5b104d..dc8c2f78bc 100644 --- a/linkerd.io/content/2.18/tasks/troubleshooting.md +++ b/linkerd.io/content/2.18/tasks/troubleshooting.md @@ -1272,7 +1272,7 @@ Example failure: Ensure that all the CNI pods are running: ```bash -$ kubectl get po -n linkerd-cn +$ kubectl get po -n linkerd-cni NAME READY STATUS RESTARTS AGE linkerd-cni-rzp2q 1/1 Running 0 9m20s linkerd-cni-mf564 1/1 Running 0 9m22s diff --git a/linkerd.io/content/2.19/reference/iptables.md b/linkerd.io/content/2.19/reference/iptables.md index 67a7ea89de..c207bd01d4 100644 --- a/linkerd.io/content/2.19/reference/iptables.md +++ b/linkerd.io/content/2.19/reference/iptables.md @@ -164,7 +164,7 @@ Alternatively, if you want to inspect the iptables rules created for a pod, you can retrieve them through the following command: ```bash -$ kubectl -n logs linkerd-init +$ kubectl -n logs linkerd-init # where is the name of the pod # you want to see the iptables rules for ``` diff --git a/linkerd.io/content/2.19/tasks/troubleshooting.md b/linkerd.io/content/2.19/tasks/troubleshooting.md index baaa71e206..4131ad328f 100644 --- a/linkerd.io/content/2.19/tasks/troubleshooting.md +++ b/linkerd.io/content/2.19/tasks/troubleshooting.md @@ -1272,7 +1272,7 @@ Example failure: Ensure that all the CNI pods are running: ```bash -$ kubectl get po -n linkerd-cn +$ kubectl get po -n linkerd-cni NAME READY STATUS RESTARTS AGE linkerd-cni-rzp2q 1/1 Running 0 9m20s linkerd-cni-mf564 1/1 Running 0 9m22s