Skip to content
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

Resizing of NFS share. #21

Closed
simonpie opened this issue Apr 24, 2017 · 13 comments
Closed

Resizing of NFS share. #21

simonpie opened this issue Apr 24, 2017 · 13 comments

Comments

@simonpie
Copy link

Hello,

Trident does not resize a volume on the NetApp filer when the pvc is changed in kubernetes. In an ideal world, I would love for trident to catch the pvc change and push it to the filer if possible.

I am using trident to create shares on a dedicated NFS SVM.

@adkerr
Copy link
Contributor

adkerr commented Apr 24, 2017

Internally tracked by [US2481]

@kangarlou
Copy link
Contributor

kangarlou commented Apr 25, 2017

There is currently no mechanism in Kubernetes to update PVs or storage classes and they should be treated as immutable objects. The need for resizing a PV/volume is well known and there is a proposal (Dynamic changes to PVs) that looks into the more general problem of updating PVs. While it's possible to extend Trident to support resizing PVs/volumes before Kubernetes supports such capability via updates to PVCs, any such effort should take into account possible implications on other components and activities (e.g., storage quota management by Kubernetes).

@dutchiechris
Copy link
Contributor

Just a note that resizing of PVs if capacity of PVC is increased is targeted for k8s 1.8; see kubernetes/enhancements#284 and Grow design proposal

In the design proposal it says NFS and iSCSI would not support resize though. I'm not sure if this is relevant if Trident manages (out of tree), or if maybe if k8s will reject an edit because it thinks the underlying NFS/iSCSI PV type doesn't support it. Could be something to check with those contributing the feature...

@acsulli
Copy link

acsulli commented Apr 10, 2018

+1 for this from a(nother) customer.

Also, the Kubernetes feature request @dutchiechris referenced has been updated to reflect target timelines (1.11 beta, 1.12 GA).

@wavezhang
Copy link
Contributor

+1, we need this feature too

@tothebit9
Copy link

+1 we are looking forward to this feature. : )

@ghost
Copy link

ghost commented Jun 26, 2018

+1

2 similar comments
@ivnilv
Copy link

ivnilv commented Jun 28, 2018

+1

@hartman17
Copy link

+1

@kangarlou
Copy link
Contributor

For volume resize to work with Trident, we need to patch k8s upstream to allow resizing NFS and iSCSI PVs. I'm working on this patch, but this means you should expect volume resize with k8s 1.12 at the earliest.

@winggundamth
Copy link

@kangarlou Can you post pull request on upstream so we can track the progress :)

@kangarlou
Copy link
Contributor

@winggundamth You can follow the PR here: kubernetes/kubernetes#66780

@NetApp NetApp deleted a comment from netapp-ci Aug 6, 2018
@NetApp NetApp deleted a comment from netapp-ci Aug 6, 2018
@canhnt
Copy link

canhnt commented Aug 15, 2018

+1 We are waiting for this feature

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests