-
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
[regression] Fix provisioning volume for ephemeral-mode workspaces. #14768
Conversation
E2E Happy path tests of Eclipse Che Single User on K8S (minikube v1.1.1) has failed:
|
E2E tests of Eclipse Che Multiuser on OCP has been successful:
|
crw-ci-test |
E2E Happy path tests of Eclipse Che Single User on K8S (minikube v1.1.1) has failed:
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
crw-ci-test |
E2E Happy path tests of Eclipse Che Single User on K8S (minikube v1.1.1) has failed:
|
crw-ci-test |
E2E Happy path tests of Eclipse Che Single User on K8S (minikube v1.1.1) has failed:
|
@amisevsk: E2E tests hasn't shown regression. |
@amisevsk: there is fixup of Happy path tests in master branch. You can take that changes an rerun the tests. |
Commit dd47af6 changes the way that certain volumes are handled; rather than storing the volume information in the relevant container's machine, it is stored in the environment's pods directly. To accomodate this, the EphemeralWorkspaceAdapter needs to pull the list of PVCs it provisions from the environment rather than machines. Signed-off-by: Angel Misevski <amisevsk@redhat.com>
Signed-off-by: Angel Misevski <amisevsk@redhat.com>
cfc262c
to
44ef65f
Compare
Thanks @dmytro-ndp |
E2E Happy path tests of Eclipse Che Single User on K8S (minikube v1.1.1) has been successful:
|
E2E tests of Eclipse Che Multiuser on OCP has been successful:
|
What does this PR do?
Fixes provisioning of volumes for ephemeral workspaces (#14749).
It also brings the
EphemeralWorkspaceAdapter
more in line withUniqueWorkspacePVCProvisioner
, which I think is an overall good change.Background
PR #14539 modified the way that certain volumes are stored in the environment: it removed adding plugin volumes to the plugin's corresponding machine and instead placed them in the pod's container directly in order to support ephemeral mode volumes for workspace plugins. This means that the
plugins
volume added for every sidecar is no longer in the machine and instead attached to each container.The
EphemeralWorkspaceAdapter
was working off a previous assumption -- that all workspace volumes could be found in the list of machines in the environment -- and used that fact to reconcile workspace volumes (for each volume in machine, update the corresponding pod to use emptyDir). This meant that theplugins
volume was not being provisioned at all (and thus had no subpath assigned).This PR changes
EphemeralWorkspaceAdapter
to be more in line withUniqueWorkspacePVCProvisioner
, basically doing the same thing and then converting all PVCs to EmptyDir volumes.What issues does this PR fix or reference?
#14749