Anatolii Bazko

@Divine1 You can simply delete operator pod. A new one will come up in a few seconds and a new operator image (`quay.io/eclipse/che-operator:next`) will be pulled up.

@Divine1 Try to inspect logs from a storage provisioner container. They might contain some clues.

We can implement Validating Webhook to check the CheCluster CR fields. I propose the following structure: ``` spec: gitServices: disabled: github: gitlab: ``` Where `GitHub` and `Gitlab` are dedicated structures....

That won't be possible. I thought the only one configuration of gitlab service is possible on the cluster.

But anyway, we can move to arrays: ``` spec: gitServices: github: [] gitlab: [] bitbucker: [] ```

Hello @tsadigovAgmail The steps are the following: 1. Update CheCluster CR: `spec.server.cheDebug: true` 2. Forward debug port: `chectl server:debug` 3. Connect to a `localhost:8000` to debug a remote Che server

Have a look pls https://github.com/eclipse/che/issues/21049#issuecomment-1022108499

I've prepared draft doc about installing Eclipse Che on minikube with Keycloak as OIDC provider. It might give some hints about configuring it for other Kubernetes providers. [1] https://github.com/eclipse-che/che-docs/pull/2408

I don't understand how it correlates with the current CheCluster CR configuration ```yaml workspaces: storage: pvc: claimSize: storageClass: pvcStrategy: ```

Catalog source to test: `docker.io/abazko/catalog:21405` Started subscription: ```yaml apiVersion: operators.coreos.com/v1alpha1 kind: Subscription metadata: name: eclipse-che-subscription namespace: openshift-operators spec: channel: next installPlanApproval: Manual name: eclipse-che-preview-openshift source: eclipse-che-custom-catalog-source sourceNamespace: openshift-operators startingCSV: eclipse-che-preview-openshift.v7.50.0-621.next...