-
Notifications
You must be signed in to change notification settings - Fork 138
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
[feature request] CSI SMB Volume Expansion #347
Comments
it's not supported yet, implement a dummy volume expansion may solve this issue. This SMB driver actually does not manage volume capacity actually, does a dummy volume expansion work for you? |
What steps can be taken to expand the volume? |
@gavin-ellis it's not supported |
@andyzhangx what do you mean by a dummy expansion and how would that be achieved? |
@andyzhangx this driver could not expand the real volume size, if you input a larger volume size, this driver would just return success, that's called dummy expansion, not sure whether it's reasonable for such behavior. |
The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs. This bot triages issues and PRs according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs. This bot triages issues and PRs according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle rotten |
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs. This bot triages issues and PRs according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /close |
@k8s-triage-robot: Closing this issue. In response to this:
Instructions 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/test-infra repository. |
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs. This bot triages issues and PRs according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /close |
@k8s-triage-robot: Closing this issue. In response to this:
Instructions 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/test-infra repository. |
Does this mean if I give 100 Gi capacity in PV and 10Gi PVC storage, I can store more than that if the underlying SMB server has storage? Is this setting required to use the driver or just leave it empty to have all the storage on SMB server be used? |
@joymon the pvc capacity does not enforce the actual data size, it's only for pv/pvc matching. |
fixed by #881 |
Tried to expand allocated PVC by editing capacity:
Update the PVC and underlying PV:
Create a PVC via YAML and redeploy the PVC after updating the capacity:
Environment:
kubectl version
): 1.20The text was updated successfully, but these errors were encountered: