gRPC or HTTP/2 Ingress Connectivity in OpenShift Container Platform
Sumit Shatwara
Sr. Solutions Engineer at Neo4j | Transforming Businesses with Graph and Gen AI technologies
OpenShift Container Platform 4.5 or later now provides end-to-end proxying of HTTP/2 traffic with the help of HAProxy which is the default Ingress Controller in cluster. You can create gRPC enabled routes to secure and route gRPC traffic over HTTP/2. This capability allows application developers and teams to leverage HTTP/2 protocol functionalities, including single connection, header compression, binary streams, and more.
HTTP/2 connectivity can be enabled for an individual Ingress Controller (default is HAProxy) in OpenShift or for the entire OpenShift cluster. To enable the use of HTTP/2 for the connection from the client to HAProxy, an OpenShift route must specify a custom certificate that needs to be generated using OpenSSL or procured from a trusted certificate authority. A route that uses the default certificate cannot use HTTP/2 connectivity. This restriction is essential to remove issues from connection coalescing, where the client re-uses a connection for different routes that use the same certificate.
To read the full article and to know the steps of testing HTTP/2 Ingress Connectivity in OpenShift, visit my personal blog: Kesseract - gRPC or HTTP/2 Ingress Connectivity in OpenShift Container Platform