On minikube, not able to start a workspace with che installed with chectl next

Describe the bug

On a minikube cluster, I’m not able to start a workspace with Che installed with chectl next due to the workspace pod terminating:

I’m not able to reproduce this issue on an OpenShift environment.

Che version

next (development version)

Steps to reproduce

1. Start a minikube cluster:

minikube start --addons=ingress --vm=true --cpus=4 --memory=16384

1. Deploy che with chectl next channel:

chectl server:deploy -p minikube

1. After installation is complete, open the Che dashboard and start any sample project.

2. The workspace does not start. The workspace pod terminates due to a failing init container: remote-runtime-injector:

$ kubectl get event --namespace admin-che --field-selector involvedObject.name=workspace63360a48062b4ea8-b548f9cd8-p8nqp
LAST SEEN   TYPE      REASON          OBJECT                                          MESSAGE
5s          Normal    Scheduled       pod/workspace63360a48062b4ea8-b548f9cd8-p8nqp   Successfully assigned admin-che/workspace63360a48062b4ea8-b548f9cd8-p8nqp to minikube
4s          Normal    Pulling         pod/workspace63360a48062b4ea8-b548f9cd8-p8nqp   Pulling image "quay.io/eclipse/che-theia-endpoint-runtime-binary:next"
4s          Normal    Pulled          pod/workspace63360a48062b4ea8-b548f9cd8-p8nqp   Successfully pulled image "quay.io/eclipse/che-theia-endpoint-runtime-binary:next" in 428.49452ms
3s          Normal    Created         pod/workspace63360a48062b4ea8-b548f9cd8-p8nqp   Created container remote-runtime-injector
3s          Normal    Started         pod/workspace63360a48062b4ea8-b548f9cd8-p8nqp   Started container remote-runtime-injector
3s          Normal    Killing         pod/workspace63360a48062b4ea8-b548f9cd8-p8nqp   Stopping container remote-runtime-injector
1s          Normal    Killing         pod/workspace63360a48062b4ea8-b548f9cd8-p8nqp   Stopping container remote-runtime-injector

Expected behavior

The workspace pod should not terminate. The workspace should start and the editor should open.

Runtime

minikube

Screenshots

No response

Installation method

chectl/next

Environment

macOS

Eclipse Che Logs

No response

Additional context

No response

[dkwon17]

I cannot reproduce this issue on chectl next anymore after the DWO update on che-operator, but I experience this issue on chectl stable (Che 7.51) on minikube.

A temporary workaround that I’ve used to get workspaces starting on minikube with Che 7.51 was to update DWO by running:

$ DWO_VERSION=v0.15.2
$ kubectl patch deployment devworkspace-controller-manager -n devworkspace-controller --patch '{"spec": {"template": {"spec": {"containers": [{"name": "devworkspace-controller","image": "quay.io/devfile/devworkspace-controller:'${DWO_VERSION}'", "env": [{"name": "RELATED_IMAGE_devworkspace_webhook_server","value": "quay.io/devfile/devworkspace-controller:'${DWO_VERSION}'"}, {"name": "RELATED_IMAGE_project_clone", "value": "quay.io/devfile/project-clone:'${DWO_VERSION}'"}]}]}}}}';

[dkwon17]

Hi @tolusha thank you for the reminder, we can close this issue