Skip to content

docs(ingress): note that ingress pods must not use hostNetwork mode #2156

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
Retr0-XD wants to merge 1 commit into
base: main
Choose a base branch
from
Open

docs(ingress): note that ingress pods must not use hostNetwork mode #2156

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
10 changes: 10 additions & 0 deletions linkerd.io/content/2.11/tasks/using-ingress.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -49,6 +49,16 @@ full set of metrics and mTLS support.

{{< /note >}}

{{< note >}}

Ingress controller pods must not run in `hostNetwork` mode. When a pod uses
`hostNetwork: true`, the Linkerd proxy sidecar is not injected, so the pod
cannot participate in the mesh. If your ingress controller is deployed with
`hostNetwork` enabled (for example, the default for Rancher RKE2's
`rke2-ingress-nginx`), disable it or switch to an ingress configuration that
allows regular pod networking.

{{< /note >}}
## Ambassador (aka Emissary) {#ambassador}

Ambassador can be meshed normally. An example manifest for configuring the
Expand Down