Skip to content

Support ControllerModifyVolume #1693

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

Closed
sunnylovestiramisu opened this issue Apr 30, 2024 · 2 comments · Fixed by #1801 · May be fixed by maxkimambo/gcp-compute-persistent-disk-csi-driver#1
Closed

Support ControllerModifyVolume #1693

sunnylovestiramisu opened this issue Apr 30, 2024 · 2 comments · Fixed by #1801 · May be fixed by maxkimambo/gcp-compute-persistent-disk-csi-driver#1
Labels
lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.

Comments

@sunnylovestiramisu
Copy link
Contributor

sunnylovestiramisu commented Apr 30, 2024

sig-storage added the support for ControllerModifyVolume in kep-3751(still an alpha feature). This feature adds the support of modifying certain volume parameters after volume creation in Kubernetes.

gcp-compute-persistent-disk-csi-driver should support this feature so that customers can update volume attributes after volume creation.

The tasks include:

  1. Implement ControllerModifyVolume in the controller, the underlying GCE API is disks.update
  2. Test coverage including unit tests and end to end test.
@k8s-triage-robot
Copy link

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

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jul 29, 2024
@k8s-triage-robot
Copy link

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-ci-robot k8s-ci-robot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Aug 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.
Projects
None yet
3 participants