Skip to content

[PVC] Prebuild+PVC, user's account without PVC, open from prebuild, still use PVC #12463

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

Closed
Tracked by #7901
jenting opened this issue Aug 29, 2022 · 6 comments
Closed
Tracked by #7901
Labels
team: workspace Issue belongs to the Workspace team type: bug Something isn't working

Comments

@jenting
Copy link
Contributor

jenting commented Aug 29, 2022

Bug description

Prebuild+PVC, user's account without PVC, open from prebuild, still use PVC

Steps to reproduce

  • Create the project with prebuild and enable PVC
  • The user account does not enable PVC
  • The user open the workspace from prebuild
  • The workspace still uses PVC

Workspace affected

No response

Expected behavior

No response

Example repository

No response

Anything else?

#7901

@jenting jenting added the type: bug Something isn't working label Aug 29, 2022
@jenting jenting added the team: workspace Issue belongs to the Workspace team label Aug 29, 2022
@kylos101
Copy link
Contributor

@jenting this is expected behavior, cc: @sagor999 , any regular workspace opened from a project's prebuild, where PVC is enabled, will also be PVC (regardless of user setting). Closing for now and removing from our project. Please reopen if you disagree.

@kylos101 kylos101 closed this as not planned Won't fix, can't repro, duplicate, stale Aug 30, 2022
@kylos101 kylos101 moved this to Awaiting Deployment in 🌌 Workspace Team Aug 30, 2022
@jenting
Copy link
Contributor Author

jenting commented Aug 30, 2022

🤔 I'm not agree because it should open without PVC and since there is no prebuild, opening the workspace should fall back to git clone.

@sagor999
Copy link
Contributor

This was intentional choice.
We want to make it easy to enroll users into PVC.
So we have two toggles for that:

  1. Feature flag in user settings that allows to use PVC for any workspace that user opens.
  2. Project settings flag that enables PVC for prebuilds and forces any user that opens such prebuild to also use PVC.

Otherwise, if we were to allow user to open PVC prebuild, but user does not have PVC enabled, now we would need to implement the feature of extracting data from PVC and somehow shoveling it into GCS which then gets uploaded into workspace (complicated), or as you suggested @jenting, fall back to git clone, but then user will not get any benefit from PVC use at all. Effectively that user will not be able to use prebuilds, and will not be able to enroll in PVC, since feature flags enablement is an admin feature. So user experience in that case would not be great in my opinion.

@jenting
Copy link
Contributor Author

jenting commented Aug 30, 2022

Make sense, the only left concern is if we enable the prebuilds for gitpod projects, and we haven't enable the users and customers PVC yet.
Then, all the users who open the workspace with the gitpod projects, they will benefit the PVC feature. It makes the user suddenly uses the PVC feature, and I think we should have a way to inform the users.

WDYT?

@sagor999
Copy link
Contributor

It would be potentially good to indicate to user that they are using PVC, but at the same time, what they really gonna do with that information?
Our storage backing is internal. In theory, it should not matter what we are using, GCS or PVC, both should be transparent to the user.

@jenting
Copy link
Contributor Author

jenting commented Aug 30, 2022

Okay, agree on you.
So, let's keep this issue close now, and if we have users have concerns in the future, let's reopen it.
Thank for all your feedback 🙏

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
team: workspace Issue belongs to the Workspace team type: bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants