Problem Statement
The ingress docs (docs/kubernetes/ingress.mdx) only cover Envoy Gateway. On OpenShift, Envoy Gateway cannot be installed because the Ingress Operator manages Gateway API CRDs and rejects third-party installations. Users following the ingress guide on OpenShift hit an error with no guidance on what to do instead.
Proposed Design
Add a <Note> callout at the top of docs/kubernetes/ingress.mdx directing OpenShift users to the OpenShift-specific guide:
<Note>
On OpenShift, the Ingress Operator manages Gateway API CRDs and Envoy Gateway cannot be installed.
Refer to [OpenShift — Gateway Connection](/kubernetes/openshift/gateway-connection) for OpenShift-specific
ingress options including reencrypt Routes and the Istio-based Gateway API controller.
</Note>
Changes required
docs/kubernetes/ingress.mdx — add the <Note> after the introductory paragraph (before "## Install Envoy Gateway")
Alternatives Considered
-
Add a full OpenShift section to ingress.mdx: Would duplicate content already covered in docs/kubernetes/openshift/gateway-connection.mdx. A cross-reference note is sufficient.
-
Do nothing, rely on the OpenShift section: Users coming from the Kubernetes nav sidebar would land on ingress.mdx first and not know to check the OpenShift section.
Problem Statement
The ingress docs (
docs/kubernetes/ingress.mdx) only cover Envoy Gateway. On OpenShift, Envoy Gateway cannot be installed because the Ingress Operator manages Gateway API CRDs and rejects third-party installations. Users following the ingress guide on OpenShift hit an error with no guidance on what to do instead.Proposed Design
Add a
<Note>callout at the top ofdocs/kubernetes/ingress.mdxdirecting OpenShift users to the OpenShift-specific guide:Changes required
docs/kubernetes/ingress.mdx— add the<Note>after the introductory paragraph (before "## Install Envoy Gateway")Alternatives Considered
Add a full OpenShift section to
ingress.mdx: Would duplicate content already covered indocs/kubernetes/openshift/gateway-connection.mdx. A cross-reference note is sufficient.Do nothing, rely on the OpenShift section: Users coming from the Kubernetes nav sidebar would land on
ingress.mdxfirst and not know to check the OpenShift section.