Eclipse Che: unable to install Eclipse Che with helm chart in k8s about che HOT 6 CLOSED

This is great!!!
Now I am able to successfully install che on k8s..
U made my day!!
Many thanks @tolusha
Debkanta

from che.

Have you configured OIDC identity provider before deploying Eclipse Che?

Please take into account, when chectl deploys Eclipse Che on minikube, then it installs and configures dex as OIDC identity provider.

from che.

Yes I did and added the details in the CRD.
My OIDC is keycloak

TR
Debkanta

from che.

Hi @tolusha I have configured OIDC in k8s (/etc/kubernetes/manifests/kube-apiserver.yaml)

• --oidc-issuer-url=https:///auth/realms/kubernetes-che-realm
  • --oidc-client-id=kube-client-id
  • --oidc-username-claim=email
    In same K8s server the eclipse che version 7.83 was successfully installed with chectl but I am struggling to install it with helm chart.
    The operator itself is failing after sometime:
    helm install my-eclipse-che eclipse-che/eclipse-che --version 7.83.0 -n eclipse-che
    The operator is up initially, but after 4/5 mins it is in error state:
    2024-03-22T17:51:53Z ERROR Reconciler error {"controller": "checluster", "controllerGroup": "org.eclipse.che", "controllerKind": "CheCluster", "CheCluster": {"name":"eclipse-che","namespace":"eclipse-che"}, "namespace": "eclipse-che", "name": "eclipse-che", "reconcileID": "3c15e639-62c3-4636-ad3c-431c65f874ce", "error": "no matches for kind "DevWorkspaceOperatorConfig" in version "controller.devfile.io/v1alpha1""}

---Last few error lines -------
2024-03-22T18:02:33Z ERROR controller-runtime.source if kind is a CRD, it should be installed before calling Start {"kind": "DevWorkspaceRouting.controller.devfile.io", "error": "no matches for kind "DevWorkspaceRouting" in version "controller.devfile.io/v1alpha1""}
sigs.k8s.io/controller-runtime/pkg/source.(*Kind).Start.func1.1
/che-operator/vendor/sigs.k8s.io/controller-runtime/pkg/source/source.go:143
k8s.io/apimachinery/pkg/util/wait.runConditionWithCrashProtectionWithContext
/che-operator/vendor/k8s.io/apimachinery/pkg/util/wait/wait.go:235
k8s.io/apimachinery/pkg/util/wait.WaitForWithContext
/che-operator/vendor/k8s.io/apimachinery/pkg/util/wait/wait.go:662
k8s.io/apimachinery/pkg/util/wait.poll
/che-operator/vendor/k8s.io/apimachinery/pkg/util/wait/wait.go:596
k8s.io/apimachinery/pkg/util/wait.PollImmediateUntilWithContext
/che-operator/vendor/k8s.io/apimachinery/pkg/util/wait/wait.go:547
sigs.k8s.io/controller-runtime/pkg/source.(*Kind).Start.func1
/che-operator/vendor/sigs.k8s.io/controller-runtime/pkg/source/source.go:136
2024-03-22T18:02:43Z ERROR Could not wait for Cache to sync {"controller": "devworkspacerouting", "controllerGroup": "controller.devfile.io", "controllerKind": "DevWorkspaceRouting", "error": "failed to wait for devworkspacerouting caches to sync: timed out waiting for cache to be synced"}
sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).Start.func2.1
/che-operator/vendor/sigs.k8s.io/controller-runtime/pkg/internal/controller/controller.go:211
sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).Start.func2
/che-operator/vendor/sigs.k8s.io/controller-runtime/pkg/internal/controller/controller.go:216
sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).Start
/che-operator/vendor/sigs.k8s.io/controller-runtime/pkg/internal/controller/controller.go:242
sigs.k8s.io/controller-runtime/pkg/manager.(*runnableGroup).reconcile.func1
/che-operator/vendor/sigs.k8s.io/controller-runtime/pkg/manager/runnable_group.go:219
2024-03-22T18:02:43Z INFO Stopping and waiting for non leader election runnables
2024-03-22T18:02:43Z INFO Stopping and waiting for leader election runnables
2024-03-22T18:02:43Z INFO Shutdown signal received, waiting for all workers to finish {"controller": "namespace", "controllerGroup": "", "controllerKind": "Namespace"}
2024-03-22T18:02:43Z INFO Shutdown signal received, waiting for all workers to finish {"controller": "checluster", "controllerGroup": "org.eclipse.che", "controllerKind": "CheCluster"}
2024-03-22T18:02:43Z INFO Shutdown signal received, waiting for all workers to finish {"controller": "namespace", "controllerGroup": "", "controllerKind": "Namespace"}
2024-03-22T18:02:43Z INFO Shutdown signal received, waiting for all workers to finish {"controller": "checluster", "controllerGroup": "org.eclipse.che", "controllerKind": "CheCluster"}
2024-03-22T18:02:43Z INFO All workers finished {"controller": "namespace", "controllerGroup": "", "controllerKind": "Namespace"}
2024-03-22T18:02:43Z INFO All workers finished {"controller": "checluster", "controllerGroup": "org.eclipse.che", "controllerKind": "CheCluster"}
2024-03-22T18:02:43Z INFO All workers finished {"controller": "checluster", "controllerGroup": "org.eclipse.che", "controllerKind": "CheCluster"}
2024-03-22T18:02:43Z INFO All workers finished {"controller": "namespace", "controllerGroup": "", "controllerKind": "Namespace"}
2024-03-22T18:02:43Z INFO Stopping and waiting for caches
2024-03-22T18:02:43Z INFO Stopping and waiting for webhooks
2024-03-22T18:02:43Z INFO controller-runtime.webhook shutting down webhook server
2024-03-22T18:02:43Z INFO Wait completed, proceeding to shutdown the manager
2024-03-22T18:02:43Z ERROR setup problem running manager {"error": "failed to wait for devworkspacerouting caches to sync: timed out waiting for cache to be synced"}
main.main
/che-operator/main.go:335
runtime.main
/usr/lib/golang/src/runtime/proc.go:250

from che.

Hi @tolusha
I tried the helm installation on Minikube also but no luck here also. followed the documentation from this link:
https://eclipse.dev/che/docs/stable/administration-guide/installing-che-on-minikube-keycloak-oidc/
All went well but the helm installation command is not working:
$ helm install che
--namespace eclipse-che
--set networking.domain=$(minikube ip).nip.io
--set networking.auth.oAuthSecret=eclipse-che
--set networking.auth.oAuthClientName=k8s-client
--set networking.auth.identityProviderURL=https://keycloak.$(minikube ip).nip.io/realms/che . &&
sleep 5s &&
kubectl patch checluster/eclipse-che --patch '{"spec": {"components": {"cheServer": {"extraProperties": {"CHE_OIDC_USERNAME__CLAIM": "email"}}}}}' --type=merge -n eclipse-che

It pops up with error:
Error: INSTALLATION FAILED: Chart.yaml file is missing

Then I tried to run these below two commands for helm based deployment:
helm repo add eclipse-che https://eclipse-che.github.io/che-operator/charts
helm install my-eclipse-che eclipse-che/eclipse-che --version 7.83.0

But result is same line vanilla k8s.

For Minikube and k8s I am using latest version
minikube version: v1.32.0
and k8s is v1.29

It is because of version?

TR
Debkanta

from che.

It seems DWO hasn't been installed before installing eclipse-che.
Try kubectl apply -f https://raw.githubusercontent.com/devfile/devworkspace-operator/v0.26.0/deploy/deployment/kubernetes/combined.yaml

2024-03-22T17:51:53Z ERROR Reconciler error {"controller": "checluster", "controllerGroup": "org.eclipse.che", "controllerKind": "CheCluster", "CheCluster": {"name":"eclipse-che","namespace":"eclipse-che"}, "namespace": "eclipse-che", "name": "eclipse-che", "reconcileID": "3c15e639-62c3-4636-ad3c-431c65f874ce", "error": "no matches for kind "DevWorkspaceOperatorConfig" in version "controller.devfile.io/v1alpha1""}

from che.