You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: modules/ossm-rn-new-features.adoc
+30-1Lines changed: 30 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -242,8 +242,22 @@ This release marks the end of support for {SMProductShortName} Control Planes ba
242
242
* Gateway injection is not a supported feature.
243
243
244
244
=== 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[]
246
247
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.
To enable the feature, set the following environment variables for the `Istiod` container in `ServiceMeshControlPlane`:
248
262
249
263
[source,yaml]
@@ -261,6 +275,21 @@ spec:
261
275
----
262
276
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`).
263
277
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
+
264
293
== New features {SMProductName} 2.1.5.2
265
294
266
295
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