Anatolii Bazko

That's strange. What is your che-operator image: `kubectl get deployment che-operator -n eclipse-che -o="jsonpath={.spec.template.spec.containers[0].image}`

Could you also check as well `kubectl get namespace devworkspace-controller -o jsonpath="{.metadata.annotations}"`

I am out of ideas. Could you check this please? `kubectl get deployment che-operator -n eclipse-che -o json | jq -r '.spec.template.spec.containers[0].env[] | select(.name=="RELATED_IMAGE_devworkspace_controller")'` `kubectl get checluster eclipse-che -n eclipse-che...

Hello @Divine1 It is v2 because of `apiVersion: org.eclipse.che/v2`

I think the correct issuer url must be the following: `https:///realms/` for instance `https://keycloak.192.168.59.253.nip.io/realms/che`

I've prepared a draft script how to setup keycloak as OIDC provider on minikube and deploy Eclipse Che. Could you check if it can shed a light on your problem?...

@anshumaanyadav-neudesic Sorry for later answer. You have to reconfigure minikube api server to use another OIDC provider, for instance: ```bash KEYCLOAK_HOST= KEYCLOAK_REALM= KEYCLOAK_CLIENT_ID= KEYCLOAK_CA_CERT_PATH= minikube ssh sudo "mkdir -p /etc/ca-certificates"...

Here is a doc explaining how to use external Keycloak with Eclipse Che https://www.eclipse.org/che/docs/stable/administration-guide/installing-che-on-minikube-keycloak-oidc/

It is nice to have but I don't have spare time to resolve conflicts.

@l0rd I can confirm: 1. This is not related to the https://github.com/eclipse/che/issues/20614 2. This is still relevant even after the switch to the DevWorkspace