Skip to content

docs: fix typos: namespace and linkerd-cni in iptables and troubleshooting guide #2090

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
bezarsnba wants to merge 3 commits into
base: main
Choose a base branch
from
Open

docs: fix typos: namespace and linkerd-cni in iptables and troubleshooting guide #2090

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
b9b5b6f
docs: Fix typos in documentation across versions
bezarsnba Feb 17, 2026
b629b99
fix version 2.19
bezarsnba Feb 17, 2026
bf519eb
Merge branch 'main' into bezarsnba/fix-typo
bezarsnba Mar 31, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion linkerd.io/content/2-edge/reference/iptables.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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 <namesppace> logs <pod-name> linkerd-init
$ kubectl -n <namespace> logs <pod-name> linkerd-init
# where <pod-name> is the name of the pod
# you want to see the iptables rules for
```
Expand Down
2 changes: 1 addition & 1 deletion linkerd.io/content/2-edge/tasks/troubleshooting.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down
2 changes: 1 addition & 1 deletion linkerd.io/content/2.10/tasks/troubleshooting.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down
2 changes: 1 addition & 1 deletion linkerd.io/content/2.11/reference/iptables.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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 <namesppace> logs <pod-name> linkerd-init
$ kubectl -n <namespace> logs <pod-name> linkerd-init
# where <pod-name> is the name of the pod
# you want to see the iptables rules for
```
Expand Down
2 changes: 1 addition & 1 deletion linkerd.io/content/2.11/tasks/troubleshooting.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down
2 changes: 1 addition & 1 deletion linkerd.io/content/2.12/reference/iptables.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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 <namesppace> logs <pod-name> linkerd-init
$ kubectl -n <namespace> logs <pod-name> linkerd-init
# where <pod-name> is the name of the pod
# you want to see the iptables rules for
```
Expand Down
2 changes: 1 addition & 1 deletion linkerd.io/content/2.12/tasks/troubleshooting.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down
2 changes: 1 addition & 1 deletion linkerd.io/content/2.13/reference/iptables.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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 <namesppace> logs <pod-name> linkerd-init
$ kubectl -n <namespace> logs <pod-name> linkerd-init
# where <pod-name> is the name of the pod
# you want to see the iptables rules for
```
Expand Down
2 changes: 1 addition & 1 deletion linkerd.io/content/2.13/tasks/troubleshooting.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down
2 changes: 1 addition & 1 deletion linkerd.io/content/2.14/reference/iptables.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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 <namesppace> logs <pod-name> linkerd-init
$ kubectl -n <namespace> logs <pod-name> linkerd-init
# where <pod-name> is the name of the pod
# you want to see the iptables rules for
```
Expand Down
2 changes: 1 addition & 1 deletion linkerd.io/content/2.14/tasks/troubleshooting.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down
2 changes: 1 addition & 1 deletion linkerd.io/content/2.15/reference/iptables.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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 <namesppace> logs <pod-name> linkerd-init
$ kubectl -n <namespace> logs <pod-name> linkerd-init
# where <pod-name> is the name of the pod
# you want to see the iptables rules for
```
Expand Down
2 changes: 1 addition & 1 deletion linkerd.io/content/2.15/tasks/troubleshooting.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down
2 changes: 1 addition & 1 deletion linkerd.io/content/2.16/reference/iptables.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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 <namesppace> logs <pod-name> linkerd-init
$ kubectl -n <namespace> logs <pod-name> linkerd-init
# where <pod-name> is the name of the pod
# you want to see the iptables rules for
```
Expand Down
2 changes: 1 addition & 1 deletion linkerd.io/content/2.16/tasks/troubleshooting.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down
2 changes: 1 addition & 1 deletion linkerd.io/content/2.17/reference/iptables.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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 <namesppace> logs <pod-name> linkerd-init
$ kubectl -n <namespace> logs <pod-name> linkerd-init
# where <pod-name> is the name of the pod
# you want to see the iptables rules for
```
Expand Down
2 changes: 1 addition & 1 deletion linkerd.io/content/2.17/tasks/troubleshooting.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down
2 changes: 1 addition & 1 deletion linkerd.io/content/2.18/reference/iptables.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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 <namesppace> logs <pod-name> linkerd-init
$ kubectl -n <namespace> logs <pod-name> linkerd-init
# where <pod-name> is the name of the pod
# you want to see the iptables rules for
```
Expand Down
2 changes: 1 addition & 1 deletion linkerd.io/content/2.18/tasks/troubleshooting.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down
2 changes: 1 addition & 1 deletion linkerd.io/content/2.19/reference/iptables.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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 <namesppace> logs <pod-name> linkerd-init
$ kubectl -n <namespace> logs <pod-name> linkerd-init
# where <pod-name> is the name of the pod
# you want to see the iptables rules for
```
Expand Down
2 changes: 1 addition & 1 deletion linkerd.io/content/2.19/tasks/troubleshooting.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down
Loading