-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
chectl server:deploy on minikube doesn't deploy DW #20620
Comments
This comment has been minimized.
This comment has been minimized.
you need the following patch to get devworkspace on kubernetes:
probably chectl can do better and ask in an interactive manner if user accept risk, but it's definitely not a bug. |
Ok thanks. Yes chectl may automatically infer that but I don't understand why the operator deploys an half-broken Che if |
I think it's not infer automatically because it's like a security risk that the user need to grant for Kubernetes installation |
What I mean is that if I enable "devworkspace" but I don't enable "unsupported k8s", the dashboard will show the devfile v2 samples but those won't work because DW is not deployed (half-broken). I think that providing a warning at the beginning of chectl deployment, maybe asking to the user to confirm that's what he wants, is better then just ignoring "devworkspace" if "unsupported k8s" is not specified. |
Describe the bug
When I try to deploy Che with using chectl with option
--workspace-engine=dev-workspace
on minikube, DevWorkspace CRD is not created:Che version
next (development version)
Steps to reproduce
minikube delete
minikube start --memory=8192 --vm=true --cpus=4 --addons=ingress
chectl update next
chectl server:deploy --telemetry=on -p minikube --workspace-engine=dev-workspace -n workspaces-server
Expected behavior
DevWorkspace CRD and controller deployed
Runtime
minikube
Screenshots
No response
Installation method
chectl/next
Environment
macOS
chectl logs
che operator logs
The text was updated successfully, but these errors were encountered: