From 588fc3ada977928f31b9836933ac98e451e85221 Mon Sep 17 00:00:00 2001 From: Retr0-XD <88275564+Retr0-XD@users.noreply.github.com> Date: Sun, 13 Sep 2026 06:53:04 +0000 Subject: [PATCH] docs(ingress): note that ingress pods must not use hostNetwork mode (#8936) Signed-off-by: Sakthi Harish --- linkerd.io/content/2.11/tasks/using-ingress.md | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/linkerd.io/content/2.11/tasks/using-ingress.md b/linkerd.io/content/2.11/tasks/using-ingress.md index 010da086f9..ea6172b593 100644 --- a/linkerd.io/content/2.11/tasks/using-ingress.md +++ b/linkerd.io/content/2.11/tasks/using-ingress.md @@ -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