Skip to content

Commit b17fa2e

Browse files
committed
OSSMDOC-720: Add more detail to Gateway API enablement docs
1 parent b410ae4 commit b17fa2e

File tree

1 file changed

+30
-1
lines changed

1 file changed

+30
-1
lines changed

modules/ossm-rn-new-features.adoc

Lines changed: 30 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -242,8 +242,22 @@ This release marks the end of support for {SMProductShortName} Control Planes ba
242242
* Gateway injection is not a supported feature.
243243

244244
=== Kubernetes Gateway API
245-
Kubernetes Gateway API is a technology preview feature that is disabled by default.
245+
:FeatureName: Kubernetes Gateway API
246+
include::snippets/technology-preview.adoc[]
246247

248+
Kubernetes Gateway API is a technology preview feature that is disabled by default. If the Kubernetes API deployment controller is disabled, you must manually deploy and link an ingress gateway to the created Gateway object.
249+
250+
If the Kubernetes API deployment controller is enabled, then an ingress gateway automatically deploys when a Gateway object is created.
251+
252+
==== Installing the Gateway API CRDs
253+
The Gateway API CRDs do not come pre-installed by default on OpenShift clusters. Install the CRDs prior to enabling Gateway API support in the SMCP.
254+
255+
[source,terminal]
256+
----
257+
$ kubectl get crd gateways.gateway.networking.k8s.io || { kubectl kustomize "github.com/kubernetes-sigs/gateway-api/config/crd?ref=v0.4.0" | kubectl apply -f -; }
258+
----
259+
260+
==== Enabling Kubernetes Gateway API
247261
To enable the feature, set the following environment variables for the `Istiod` container in `ServiceMeshControlPlane`:
248262

249263
[source,yaml]
@@ -261,6 +275,21 @@ spec:
261275
----
262276
Restricting route attachment on Gateway API listeners is possible using the `SameNamespace` or `All` settings. Istio ignores usage of label selectors in `listeners.allowedRoutes.namespaces` and reverts to the default behavior (`SameNamespace`).
263277

278+
==== Manually linking an existing gateway to a Gateway resource
279+
If the Kubernetes API deployment controller is disabled, you must manually deploy and then link an ingress gateway to the created Gateway resource.
280+
281+
[source,yaml]
282+
----
283+
apiVersion: gateway.networking.k8s.io/v1alpha2
284+
kind: Gateway
285+
metadata:
286+
name: gateway
287+
spec:
288+
addresses:
289+
- value: ingress.istio-gateways.svc.cluster.local
290+
type: Hostname
291+
----
292+
264293
== New features {SMProductName} 2.1.5.2
265294

266295
This release of {SMProductName} addresses Common Vulnerabilities and Exposures (CVEs), contains bug fixes, and is supported on OpenShift Container Platform 4.9 or later.

0 commit comments

Comments
 (0)