From aa0ac9577f474b981dbfca4cde7a35a5eff48a9b Mon Sep 17 00:00:00 2001 From: Anatolii Bazko Date: Thu, 3 Feb 2022 12:33:06 +0200 Subject: [PATCH] fix: Disable HTTP2 protocol Signed-off-by: Anatolii Bazko --- pkg/deploy/server/server_configmap.go | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/pkg/deploy/server/server_configmap.go b/pkg/deploy/server/server_configmap.go index b241ce755d..fe46be5204 100644 --- a/pkg/deploy/server/server_configmap.go +++ b/pkg/deploy/server/server_configmap.go @@ -87,6 +87,7 @@ type CheConfigMap struct { WorkspaceExposure string `json:"CHE_INFRA_KUBERNETES_SINGLEHOST_WORKSPACE_EXPOSURE"` SingleHostGatewayConfigMapLabels string `json:"CHE_INFRA_KUBERNETES_SINGLEHOST_GATEWAY_CONFIGMAP__LABELS"` CheDevWorkspacesEnabled string `json:"CHE_DEVWORKSPACES_ENABLED"` + Http2Disable string `json:"HTTP2_DISABLE"` } // GetCheConfigMapData gets env values from CR spec and returns a map with key:value @@ -265,6 +266,11 @@ func (s *CheServerReconciler) getCheConfigMapData(ctx *deploy.DeployContext) (ch WorkspaceExposure: workspaceExposure, SingleHostGatewayConfigMapLabels: singleHostGatewayConfigMapLabels, CheDevWorkspacesEnabled: strconv.FormatBool(ctx.CheCluster.Spec.DevWorkspace.Enable), + // Disable HTTP2 protocol. + // Fix issue with creating config maps on the cluster https://issues.redhat.com/browse/CRW-2677 + // The root cause is in the HTTP2 protocol support of the okttp3 library that is used by fabric8.kubernetes-client that is used by che-server + // In the past, when che-server used Java 8, HTTP1 protocol was used. Now che-sever uses Java 11 + Http2Disable: strconv.FormatBool(true), } data.IdentityProviderUrl = identityProviderURL