From abff9074a2b964379efc8fc1b3e4ae753b596de1 Mon Sep 17 00:00:00 2001 From: hamza-m-masood Date: Fri, 28 Jun 2024 16:03:51 +0100 Subject: [PATCH] reword --- .../self-managed/setup/deploy/openshift/redhat-openshift.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/versioned_docs/version-8.5/self-managed/setup/deploy/openshift/redhat-openshift.md b/versioned_docs/version-8.5/self-managed/setup/deploy/openshift/redhat-openshift.md index 2e980d9cb4..73a9811f88 100644 --- a/versioned_docs/version-8.5/self-managed/setup/deploy/openshift/redhat-openshift.md +++ b/versioned_docs/version-8.5/self-managed/setup/deploy/openshift/redhat-openshift.md @@ -193,7 +193,7 @@ To use these routes for the Zeebe Gateway, configure this through Ingress as wel As the Zeebe Gateway also uses `gRPC` (which relies on `HTTP/2`), [HTTP/2 Ingress Connectivity has to be enabled](https://docs.openshift.com/container-platform/latest/networking/ingress-operator.html#nw-http2-haproxy_configuring-ingress). -Also, Zeebe Gateway needs to be encrypted with tls because the connection from HAProxy to the Zeebe Gateway service can use HTTP/2 only for re-encrypt or passthrough routes and not for edge-terminated or insecure routes. +Also, Zeebe Gateway should be configured to use an encrypted connection with TLS because the connection from HAProxy to the Zeebe Gateway service can use HTTP/2 only for re-encrypt or passthrough routes and not for edge-terminated or insecure routes. #### Required Steps