Skip Volume Ownership Change

[mattsmithdatera]

Enhancement Description

• NewPermissionChangePolicy string field in PersistentVolumeClaimVolumeSource struct and related conditional volume ownership change behavior
• Primary contact (assignee): @mattsmithdatera @gnufied
• Responsible SIGs: sig-storage
• KEP: https://github.com/kubernetes/enhancements/blob/master/keps/sig-storage/695-skip-permission-change
• Link to e2e and/or unit tests: TBD
• Reviewer(s): @saad-ali @msau42
• Approver (likely from SIG/area to which enhancement belongs): @liggitt
• Enhancement target (which target equals to which milestone):
  • Alpha release target (x.y) 1.18
  • Beta release target (x.y) 1.20
  • Stable release target (x.y)

Pull request implementing this change: kubernetes/kubernetes#73232

[mattsmithdatera]

/sig storage
/kind feature
cc @gnufied @saad-ali @msau42

[gnufied]

/sig api-machinery

[kacole2]

Hello @mattsmithdatera , I'm the Enhancement Lead for 1.15. Is this feature going to be graduating alpha/beta/stable stages in 1.15? Please let me know so it can be tracked properly and added to the spreadsheet. I also do not see a KEP. All enhancements require one to be included.

Once coding begins, please list all relevant k/k PRs in this issue so they can be tracked properly.

[justaugustus]

/assign @mattsmithdatera @gnufied

[evillgenius75]

Hi @mattsmithdatera I'm a 1.16 Enhancement Shadow. Is this feature going to be graduating alpha/beta/stable stages in 1.16? Please let me know so it can be added to the 1.16 Tracking Spreadsheetand the correct milestone and tracked label is applied.

As a reminder, every enhancement requires a KEP in an implementable state with Graduation Criteria explaining each alpha/beta/stable stages requirements. I see that the KEP #696 has yet to be merged.

Milestone dates are Enhancement Freeze 7/30 and Code Freeze 8/29.

Thank you.

[kcmartin]

Hello @mattsmithdatera / @gnufied -- 1.17 Enhancement Shadow here! 🙂

I wanted to reach out to see if this enhancement will be graduating to alpha/beta/stable in 1.17?


Please let me know so that this enhancement can be added to 1.17 tracking sheet.

Thank you!

🔔Friendly Reminder

The current release schedule is

• Monday, September 23 - Release Cycle Begins
• Tuesday, October 15, EOD PST - Enhancements Freeze
• Thursday, November 14, EOD PST - Code Freeze
• Tuesday, November 19 - Docs must be completed and reviewed
• Monday, December 9 - Kubernetes 1.17.0 Released

[gnufied]

We are not doing anything for this in 1.17, but this is a problem that we are aiming to solve for 1.18.