Skip to content
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

Make it easy for first time Che users to launch workspaces from the dashboard on Minikube #23317

Open
rsriniva opened this issue Jan 23, 2025 · 4 comments
Labels
kind/enhancement A feature request - must adhere to the feature request template. status/info-needed More information is needed before the issue can move into the “analyzing” state for engineering.

Comments

@rsriniva
Copy link

Is your enhancement related to a problem? Please describe

For users who are installing and evaluating Che for the first time, and usually using minikube for installing Che, the numerous examples populated in the dashboard do not work. All of them hang on the Starting IDE... phase when a workspace is launched. The workspace comes up correctly if the examples from che-samples in github are pointed to directly in the Create and Open field. The devfile links available in the devfile.io registry also do not work by cutting and pasting into the Create and Open field.

I don't know if this is a minikube thing, but it would be nice if the dashboard is populated with the correct entries so that newcomers can launch and test various runtimes and hopefully do more with Che. It's a turn off if basic things do not work after install.

Describe the solution you'd like

  • Make the dashboard samples in the default install work correctly.
  • Modify the default install to point to OpenVSX.org directly instead of the default internal plugin registry. Newcomers should be able to play with the dashboard samples and install and try some extensions
  • Change the defaults to allow newcomers to launch more than one workspace at a time. Say a conservative number like 5 should be good

Describe alternatives you've considered

No response

Additional context

No response

@rsriniva rsriniva added the kind/enhancement A feature request - must adhere to the feature request template. label Jan 23, 2025
@che-bot che-bot added the status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github. label Jan 23, 2025
@tolusha
Copy link
Contributor

tolusha commented Jan 23, 2025

Make the dashboard samples in the default install work correctly.

#23179

@tolusha
Copy link
Contributor

tolusha commented Jan 23, 2025

Modify the default install to point to OpenVSX.org directly instead of the default internal plugin registry. Newcomers should be able to play with the dashboard samples and install and try some extensions

The che-plugin registry is deprecated and OpenVSX.org is the default registry already.

@rsriniva
Copy link
Author

Modify the default install to point to OpenVSX.org directly instead of the default internal plugin registry. Newcomers should be able to play with the dashboard samples and install and try some extensions

The che-plugin registry is deprecated and OpenVSX.org is the default registry already.

I ran the install using chectl today in the morning. It installed 7.97.0 of Che. The CheCluster CR does not list OpenVSX and plugins did not install in my workspace that were declared in .vscode/extensions.json

@svor svor changed the title Make it easy for first time Che users to launch workspaces from the dashboard Make it easy for first time Che users to launch workspaces from the dashboard on Minikube Jan 23, 2025
@svor svor added the status/info-needed More information is needed before the issue can move into the “analyzing” state for engineering. label Jan 23, 2025
@svor
Copy link
Contributor

svor commented Jan 23, 2025

Che uses https://open-vsx.org as a default extensions registry and you don't need to set it in the CheCluster CR:

Image

Are there any extensions visible in the Extensions view on your instance? If not, could you please check the browser console logs?

@svor svor removed the status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github. label Jan 23, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/enhancement A feature request - must adhere to the feature request template. status/info-needed More information is needed before the issue can move into the “analyzing” state for engineering.
Projects
None yet
Development

No branches or pull requests

4 participants