Cannot access workspace after upgrading from 7.0 to 7.1/7.2

I have just upgraded our helm deployment from 7.0 to 7.1 (and latest master) and we now get a bunch of CORS/Jwtproxy errors and can’t access any workspaces 😦

Screenshots

Che version

• latest
• nightly
• other: 7.1.0 and above

Steps to reproduce

Launch any workspace.

Expected behaviour

Be able to launch a workspace and access it via a web browser

Runtime

• kubernetes (include output of kubectl version)

kubectl version
Client Version: version.Info{Major:"1", Minor:"13", GitVersion:"v1.13.9", GitCommit:"3e4f6a92de5f259ef313ad876bb008897f6a98f0", GitTreeState:"clean", BuildDate:"2019-08-05T09:22:00Z", GoVersion:"go1.11.5", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"14", GitVersion:"v1.14.6", GitCommit:"96fac5cd13a5dc064f7d9f4f23030a6aeface6cc", GitTreeState:"clean", BuildDate:"2019-08-19T11:05:16Z", GoVersion:"go1.12.9", Compiler:"gc", Platform:"linux/amd64"}

Installation method

Helm charts via Rancher

Environment

• my computer
  • Linux
• Cloud
  • Amazon

Additional context

The only changes from default helm chart are listed below

global: 
    cheWorkspacesNamespace: "che-hw4gt"
    ingressDomain: "che.che-test.XYZ.com"
    multiuser: "true"

CHE_INFRA_KUBERNETES_POD_SECURITY__CONTEXT_FS__GROUP: "0"
CHE_INFRA_KUBERNETES_POD_SECURITY__CONTEXT_RUN__AS__USER: "0"

[disaster37]

Hi, it’s work like a charm, thanks 😉

[skabashnyuk]

@davidwindell apparently we don’t have it.