[feature request] CSI SMB Volume Expansion

[san360]

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:

• CSI Driver version: 1.20
• Kubernetes version (use kubectl version): 1.20
• OS (e.g. from /etc/os-release): Linux, Ubuntu

[andyzhangx]

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?

[gavin-ellis]

What steps can be taken to expand the volume?
Is the spec.storage.capacity value not enforced?
Does increasing the capacity in the PVC work?

[andyzhangx]

What steps can be taken to expand the volume? Is the spec.storage.capacity value not enforced? Does increasing the capacity in the PVC work?

@gavin-ellis it's not supported

[winromulus]

@andyzhangx what do you mean by a dummy expansion and how would that be achieved?

[andyzhangx]

@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.

[k8s-triage-robot]

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:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[k8s-triage-robot]

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:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

[k8s-triage-robot]

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:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Reopen this issue or PR with /reopen
• Mark this issue or PR as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close

[k8s-ci-robot]

@k8s-triage-robot: Closing this issue.

In response to this:

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:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Reopen this issue or PR with /reopen
• Mark this issue or PR as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close

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.