-
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
Faster workspace startup as a result of avoiding changes to DevWorkspace CR after it has started #21664
Comments
@olexii4 I was able to reproduce the issue on Dev Spaces 3.2 even though the fix was backported - eclipse-che/che-dashboard#626 Please, find the events when an alternative editor (VSCode) is selected for Getting Started samples |
@ibuziuk I cannot reproduce it. |
thanks, let's close in this case |
@olexii4 it seems that in 3.3 on workspaces.openshift.com we still have this behavior when starting getting-started samples: Reproduced with NodeJs MongoDB |
Need to verify again after workspaces.openshift.com upgrades to 3.5 and close if not reproducible |
Verified against workspaces.openshift.com Closing |
Describe the bug
During startup looks like dashboard is patching DevWorkspace which results in replica set being scaled down resulting in a much slower workspace startup
the
Che version
7.50
Steps to reproduce
Expected behavior
replica set is scaled up once during workspace startup
Runtime
OpenShift
Screenshots
No response
Installation method
OperatorHub
Environment
Dev Sandbox (workspaces.openshift.com)
Release Notes Text
The startup times of workspaces that have a persistent volume attached (the default) has been significantly improved.
The text was updated successfully, but these errors were encountered: