-
Notifications
You must be signed in to change notification settings - Fork 97
feat : Add storageAccessMode to PVC che cluster types #2004
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
feat : Add storageAccessMode to PVC che cluster types #2004
Conversation
|
Hi @rohanKanojia. Thanks for your PR. I'm waiting for a eclipse-che member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
ce445f3 to
94b67c3
Compare
Update github.com/devfile/devworkspace-operator dependency to v0.35.0 Signed-off-by: Rohan Kumar <[email protected]>
….35.0 bump Signed-off-by: Rohan Kumar <[email protected]>
Signed-off-by: Rohan Kumar <[email protected]>
…concile While updating WorkspaceConfig with CheClusterDevEnvironment also set StorageAccessMode if present. Signed-off-by: Rohan Kumar <[email protected]>
94b67c3 to
e2c3bf9
Compare
|
/retest |
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: rohanKanojia, tolusha The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
|
@rohanKanojia |
| // It is used to specify PersistentVolume access mode type to RWO/RWX when using per-user strategy, allowing | ||
| // user to re-use volume across multiple workspaces. | ||
| // | ||
| // It defaults to ReadWriteOnce if not specified |
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.
The default ReadWriteOnce is not being used in this case,
For example, if I set:
storage:
perUserStrategyPvcConfig:
storageAccessMode:
- ReadWriteMany
pvcStrategy: per-user
And then if I remove perUserStrategyPvcConfig:
storage:
pvcStrategy: per-user
the DWOC still has ReadWriteMany:
apiVersion: controller.devfile.io/v1alpha1
config:
workspace:
storageAccessMode:
- ReadWriteMany
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.
storageClass and claimSize has the same behaviour where the defaults aren't applied:
| if pvc.StorageClass != "" { |
| if pvc.ClaimSize != "" { |
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.
I've created this issue for addressing it eclipse-che/che#23502
What does this PR do?
This is a follow-up PR to devfile/devworkspace-operator#1430
Signed-off-by: Rohan Kumar [email protected]
Screenshot/screencast of this PR
What issues does this PR fix or reference?
It's related to this PR devfile/devworkspace-operator#1430
How to test this PR?
OpenShift
on Minikube
spec.devEnvironments.storage.perUserStrategyPvcConfig.storageAccessModeto[ "ReadOnlyMany" ]. Verify that the DWOC has the same fields:spec.devEnvironments.storage.perUserStrategyPvcConfig.storageAccessModefield. Verify that the storageAccessMode has been removed from the DWOC:PR Checklist
As the author of this Pull Request I made sure that:
What issues does this PR fix or referenceandHow to test this PRcompletedReviewers
Reviewers, please comment how you tested the PR when approving it.