Mutable PersistentVolume Node Affinity

[huww98]

Enhancement Description

• One-line enhancement description (can be used as a release note): make PersistentVolume.spec.nodeAffinity field mutable.
• Kubernetes Enhancement Proposal: https://github.com/huww98/enhancements/blob/mutable-pv-affinity/keps/sig-storage/5381-mutable-pv-affinity/README.md
• Discussion Link:
  • https://kubernetes.slack.com/archives/C8EJ01Z46/p1737707519480759
  • https://docs.google.com/document/d/1-8KEG8AjAgKznS9NFm3qWqkGyCHmvU6HVl0sk5hwoAE/edit?tab=t.0#heading=h.k4uvxr6ssid4
• Primary contact (assignee): @huww98 @iltyty
• Responsible SIGs: sig-storage
• Enhancement target (which target equals to which milestone):
  • Alpha release target (x.y): v1.35
  • Beta release target (x.y): v1.36
  • Stable release target (x.y): v1.38
• Alpha
  • KEP (k/enhancements) update PR(s): KEP-5381: Mutable PersistentVolume Node Affinity #5382
  • Code (k/k) update PR(s):
  • Docs (k/website) update PR(s):

Please keep this description up to date. This will help the Enhancement Team to track the evolution of the enhancement efficiently.

[huww98]

/sig storage

[rayandas]

Hi @huww98 👋, v1.34 Enhancements team here.

This is a reminder of the upcoming PRR Freeze on Thursday 12th June 2025.

By this date, there must be a PR open in k/enhancements with:

• The KEP's PRR questionnaire filled out.
• The kep.yaml updated with the stage, latest-milestone, and milestone struct filled out.
• A PRR approval file with the PRR approver listed for the stage the KEP is targeting.

Having the PRR questionnaire filled out by this deadline will help ensure that the PRR team has enough time to review your KEP before Enhancements Freeze on Friday 20th June 2025. For more information on the PRR process, see here.

[rayandas]

Hello again @huww98 👋, v1.34 Enhancements team here.

Just checking in as we approach enhancements freeze on 21:00 UTC Friday 20th June 2025 / 14:00 PST Friday 20th June 2025.

This enhancement is targeting stage alpha for v1.34 (correct me, if otherwise)

Here’s where this enhancement currently stands:

• KEP readme using the latest template has been merged into the k/enhancements repo.
• KEP status is marked as implementable for latest-milestone: v1.34.
• KEP readme has up-to-date graduation criteria.
• KEP has submitted a production readiness review request for approval and has a reviewer assigned.
• KEP has a production readiness review that has been completed and merged into k/enhancements. (For more information on the PRR process, check here).

For this KEP, we would need to update the following:

• I see you have a PR up: KEP-5381: Mutable PersistentVolume Node Affinity #5382, merging it to k/enhancements will unblock this KEP before the freeze.
• You need to have a Production readiness review that has been completed and merged into k/enhancements.

The status of this enhancement is marked as At risk enhancements freeze. Please keep the issue description up-to-date with appropriate stages as well.

If you anticipate missing enhancements freeze, you can file an exception request in advance.
Thank you!

[huww98]

@rayandas Thanks. After discussions, we have not reached enough agreements, and I would like to move this to 1.35.