Skip to content

Commit f051c38

Browse files
committed
with feedback, make things shorter and include links
1 parent 962f51c commit f051c38

File tree

1 file changed

+8
-2
lines changed

1 file changed

+8
-2
lines changed

release_notes/ocp-4-19-release-notes.adoc

Lines changed: 8 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -2809,13 +2809,19 @@ To save the `vmcore` file, use the `crashkernel` setting to reserve 1024 MB of m
28092809

28102810
* NFS volumes exported from VMware vSAN Files cannot be mounted by clusters running {product-title} 4.19 due to RHEL-83435. To avoid this issue, ensure that you are running VMware ESXi and vSAN at the latest patch versions of 8.0 P05, or later. (link:https://issues.redhat.com/browse/OCPBUGS-55978[OCPBUGS-55978])
28112811

2812-
* By default, `istiod` will create a ConfigMap `istio-ca-root-cert` in every namespace it watches, which can create unnecessary ConfigMaps. This behavior depends on the discoverySelectors, so that any proxy that might be injected in those namespaces has istiod's CA root certificate. This is needed for the proxies to verify the istiod's certificate when performing the initial connection. No 'normal' sidecar injections are planned. The only injection necessary is Gateway injection based on k8s Gateway API resources. This issue was fixed for Red Hat OpenShift Service Mesh 3.0.1. However, istiod does not clean up existing ConfigMaps. (link:https://issues.redhat.com/browse/OSSM-9076[OSSM-9076])
2812+
.Known Gateway API issues
2813+
2814+
* By default, `istiod` will create a ConfigMap `istio-ca-root-cert` in every namespace it watches, which can create unnecessary ConfigMaps. (link:https://issues.redhat.com/browse/OSSM-9076[OSSM-9076])
28132815

28142816
* When using Gateway API via the Cluster Ingress Operator (CIO), any Istio specific resources (e.g. VirtualService) are not allowed or supported. (link:https://issues.redhat.com/browse/OSSM-9154[OSSM-9154])
28152817

28162818
* Istio will copy all labels and annotations from your Gateway objects to the child resources it creates. (link:https://issues.redhat.com/browse/OSSM-8989[OSSM-8989])
28172819

2818-
* Two gateways can specify the same host name and are not marked as conflicted.
2820+
* Gateway API on CIO can be broken by an existing incompatible OpenShift Service Mesh (OSSM) subscription. (link:https://issues.redhat.com/browse/NE-1964[NE-1964])
2821+
2822+
* Currently Gateway API is not supported for on-premise platforms: BareMetal, VSphere, oVirt, KubeVirt, EquinixMetal, Nutanix. (link:https://issues.redhat.com/browse/NE-2010[NE-2010])
2823+
2824+
*
28192825

28202826
[id="ocp-4-19-asynchronous-errata-updates_{context}"]
28212827
== Asynchronous errata updates

0 commit comments

Comments
 (0)