Always Honor PersistentVolume Reclaim Policy

[xing-yang]

Enhancement Description

• One-line enhancement description (can be used as a release note): PersistentVolume reclaim policy should always be honored
• Kubernetes Enhancement Proposal: https://github.com/kubernetes/enhancements/tree/master/keps/sig-storage/2644-honor-pv-reclaim-policy
• Discussion Link: https://github.com/kubernetes-csi/external-provisioner/issues/546
• Primary contact (assignee): @deepakkinni @xing-yang
• Responsible SIGs: SIG-Storage
• Enhancement target (which target equals to which milestone):
  • Alpha release target (x.y): 1.23
  • Beta release target (x.y): 1.31
  • Stable release target (x.y): 1.32
• [X] Alpha
  • [x] KEP (k/enhancements) update PR(s): https://github.com/kubernetes/enhancements/pull/2680
  • [x] Code (k/k) update PR(s): https://github.com/kubernetes/kubernetes/pull/105773
  • [ ] Docs (k/website) update(s): PR submitted
• [x] Beta
  • [x] KEP (k/enhancements) update PR(s): https://github.com/kubernetes/enhancements/pull/4397
  • [x] e2e tests: https://github.com/kubernetes/kubernetes/pull/123151
  • [x] Code (k/k) update PR(s): https://github.com/kubernetes/kubernetes/pull/124842
  • [x] Docs (k/website) update(s): https://github.com/kubernetes/website/pull/46794
  • [x] Blog: https://github.com/kubernetes/website/pull/46890

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

[edithturn]

Hello @deepakkinni!

👋 from the v1.31 Communications Team!

We'd love for you to opt in to write a feature blog about your enhancement! Some reasons why you might want to write a blog for this feature include (but are not limited to) if this introduces breaking changes, is important to our users, or has been in progress for a long time and is graduating.

To opt in, let us know and open a Feature Blog placeholder PR against the website repository by 3rd July, 2024. For more information about writing a blog see the blog contribution guidelines.

Note: In your placeholder PR, use XX characters for the blog date in the front matter and file name. We will work with you on updating the PR with the publication date once we have a final number of feature blogs for this release.

[xing-yang]

Hi @edithturn, a placeholder blog PR is submitted here: https://github.com/kubernetes/website/pull/46890

[edithturn]

Hi @edithturn, a placeholder blog PR is submitted here: https://github.com/kubernetes/website/pull/46890

Hi @xing-yang, thank you for your response; please let me know if you need any help!

[prianna]

Hey again @xing-yang 👋 Enhancements team here,

Just checking in as we approach code freeze at 02:00 UTC Wednesday 24th July 2024 / 19:00 PDT Tuesday 23rd July 2024.

Here's where this enhancement currently stands:

• [x] All PRs to the Kubernetes repo that are related to your enhancement are linked in the above issue description (for tracking purposes).
• [x] All PR/s are ready to be merged (they have approved and lgtm labels applied) by the code freeze deadline. This includes tests.

With all the implementation(code related) PRs merged as per the issue description:

• https://github.com/kubernetes/kubernetes/pull/124842
• https://github.com/kubernetes/kubernetes/pull/123151

This enhancement is now marked as tracked for code freeze for the 1.31 Code Freeze!

Also, please let me know if there are other PRs in k/k we should be tracking for this KEP. As always, we are here to help if any questions come up. Thanks!

[tjons]

Hi, enhancements lead here - I inadvertently added this to the 1.32 tracking board 😀. Please readd it if you wish to progress this enhancement in 1.32.

/remove-label lead-opted-in