Loading...

XML

Word

Printable

Severity:
Important
Regression:
None
Story Points:
3
Sprint:
NE Sprint 260, NE Sprint 261, NE Sprint 262, NE Sprint 263
sprint_count:
4
Release Blocker:
Rejected
Blocked:
False
Blocked Reason:

Hide

None

Show
None
Release Note Text:

Hide
* Previously, a change in OVN-Kubernetes that standardized the `appProtocol` value `h2c` to `kubernetes.io/h2c` was not recognized by the {product-title} router. Consequently, specifying `appProtocol: kubernetes.io/h2c` on a service did not cause the router to use clear-text HTTP/2 to connect to the service endpoints. With this release, the {product-title} router was changed to handle `appProtocol: kubernetes.io/h2c` the same way as it handles `appProtocol: h2c` resolving the issue. (link:https://issues.redhat.com/browse/OCPBUGS-42972[*~~OCPBUGS-42972~~*])

Show
* Previously, a change in OVN-Kubernetes that standardized the `appProtocol` value `h2c` to `kubernetes.io/h2c` was not recognized by the {product-title} router. Consequently, specifying `appProtocol: kubernetes.io/h2c` on a service did not cause the router to use clear-text HTTP/2 to connect to the service endpoints. With this release, the {product-title} router was changed to handle `appProtocol: kubernetes.io/h2c` the same way as it handles `appProtocol: h2c` resolving the issue. (link: https://issues.redhat.com/browse/OCPBUGS-42972 [* OCPBUGS-42972 *])
Release Note Type:
Bug Fix
Release Note Status:
Done
Target Version:

4.18.0

`appProtocol: kubernetes.io/h2c` has been adopted upstream but OCP router does not support it so Serverless needs to revert its use downstream.
recently we faced an issue where we have an grpc client using an edge terminated route where alpn is empty, when we use `appProtocol: h2c` .
With the latest grpc client versions an alpn is required, see here and here. Could this be fixed as well?

links to

RHEA-2024:6122 OpenShift Container Platform 4.18.z bug fix update