Extend the disk size of NFS share

[danhul]

I used helm to deploy nfs-ganesha-provisioner in my k8s cluster. The default size of the NFS share is 124 GB. As I add more PVCs using the NFS storage class, the remaining disk space is getting less and less. I would like to extend the size of the actual NFS disk before it gets full. Any idea how that can be done?

[Shawn1874]

It doesn't look very promising that you will get a response. The project has very little documentation stating its purpose, intended goals, or any constraints and limitations of the project. If using AWS EFS or something like that then it should scale automatically if you have set that up. Since this project supposedly supports dynamic provisioning, it is unclear how it would interact with a variety of cloud providers. Perhaps posting examples of your volume claim yaml and a pod spec would help to garner a response. Also what are you doing for cleanup? As the SW runs for days, weeks, and/or months is there any type of auto-purging or cleanup being done to recover space?

[EsDmitrii]

you need to edit PVC that your statefulset created in your helm values set

storageClass:
  allowVolumeExpansion: true

than:

kubectl edit pvc <name> for each PVC in the StatefulSet, to increase its capacity.
kubectl delete sts --cascade=orphan <name> to delete the StatefulSet and leave its pods.
kubectl apply -f <name> to recreate the StatefulSet.
kubectl rollout restart sts <name> to restart the pods, one at a time. During restart, the pod's PVC will be resized.

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues 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 as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

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

/lifecycle stale

[khusseini]

you need to edit PVC that your statefulset created in your helm values set

storageClass:
  allowVolumeExpansion: true

than:

kubectl edit pvc <name> for each PVC in the StatefulSet, to increase its capacity.
kubectl delete sts --cascade=orphan <name> to delete the StatefulSet and leave its pods.
kubectl apply -f <name> to recreate the StatefulSet.
kubectl rollout restart sts <name> to restart the pods, one at a time. During restart, the pod's PVC will be resized.

@EsDmitrii Would that have an effect on existing PVCs? We have an instance running and disk space is running low. We have PVCs in use with Ganesha and I want to expand the volume, however I don't want to affect running pods. Would they be affected?

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.

This bot triages un-triaged issues 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 as fresh with /remove-lifecycle rotten
• Close this issue 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 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 with /reopen
• Mark this issue as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

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

/close not-planned

[k8s-ci-robot]

@k8s-triage-robot: Closing this issue, marking it as "Not Planned".

In response to this:

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues 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 with /reopen
• Mark this issue as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

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

/close not-planned

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.