Protect secret from deletion while it is in-use

[mkimuram]

Enhancement Description

• One-line enhancement description (can be used as a release note): Protect secret from deletion while it is in-use
• Kubernetes Enhancement Proposal: Add KEP for Secret/ConfigMap protection #2640
• Discussion Link: Protect secret from deletion while it is in-use kubernetes#101130
• Primary contact (assignee): @mkimuram
• Responsible SIGs: @kubernetes/sig-storage-feature-requests
• Enhancement target (which target equals to which milestone):
  • Alpha release target (x.y): 1.23
  • Beta release target (x.y): 1.24
  • Stable release target (x.y): 1.26
• Alpha
  • KEP (k/enhancements) update PR(s):
  • 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.

[JamesLaverack]

/stage alpha
/milestone v1.22

[reylejano]

Hi @mkimuram ,

1.22 Enhancements team here. I see that the PR for the KEP is open at the time of this comment in PR 2640.

The 1.22 Enhancements Freeze is coming up on Thursday, May 13 at 23:59:59 pst.
For an enhancement to successfully make the 1.22 Enhancement Freeze, it requires the following:

• A merged KEP README.md and kep.yaml in k/enhancements and follows the kep template
  • KEP README.md must include all sections in the template including Graduation Criteria for the stage going in to (e.g. alpha, beta, stable), a Test Plan
  • The kep.yaml must include the following key:value pairs
    • state: implementable
    • latest-milestone: "v1.22"
    • appropriate alpha, beta, stable milestones
• An approved Production Readiness Review (PRR), read this to learn how to submit a PRR

Feel free to reach out if you have any questions

[reylejano]

Hi @mkimuram, the 1.22 Enhancements Freeze starts at 23:59:59 pst today, May 13.
For this enhancement to make the 1.22 Enhancements Freeze, the changes listed in my earlier comment have to be merged by 23:59:59 pst today, May 13.

PR 2640 is open to address the changes required to make the 1.22 Enhancements Freeze but must merge by 23:59:59 pst today, May 13

[mkimuram]

/assign @xing-yang
/cc @johnbelamaric @liggitt

[JamesLaverack]

Hi @mkimuram, 1.22 Enhancements Lead here. 👋 With enhancements freeze now in effect we are removing this enhancement from the 1.22 release.

Feel free to file an exception to add this back to the release. If you plan to do so, please file this as early as possible.

Thanks!
/milestone clear

[xing-yang]

/milestone v1.23

[lauralorenz]

Hi @mkimuram! 1.23 Enhancements team here. Just checking in as we approach enhancements freeze on Thursday 09/09.

If I understand correctly you are targeting alpha stage for release 1.23.

Here's where this enhancement currently stands:

• KEP file using the latest template has been merged into the k/enhancements repo.
• KEP status is marked as implementable (filled out in PR, not merged)
• KEP has a test plan section filled out. (filled out in PR, not merged)
• KEP has up to date graduation criteria. (filled out in PR, not merged)
• KEP has a production readiness review that has been completed and merged into k/enhancements. (filled out in PR, not merged)

Starting with 1.23, we have implemented a soft freeze on production readiness reviews beginning TOMORROW, Thursday 09/02. It looks like you have your PRR questionnaire filled out in your PR and a PRR reviewer assigned, so you are on track for the soft freeze tomorrow!

Thanks!

[lauralorenz]

Hi @mkimuram! 1.23 Enhancements team here again. Just doing my rounds and I saw in #2640 (comment) that this is expected to slip the deadline for 1.23 enhancements freeze tonight. If that's true when you have a chance to confirm/remove from milestone/update the enhancements issue OP with the new targets, that would be great! Thanks!

[salaxander]

Hi, 1.23 Enhancements Lead here 👋. With enhancements freeze now in effect, this enhancement has not met the criteria for the freeze and has been removed from the milestone.

As a reminder, the criteria for enhancements freeze is:

• KEP is merged into k/enhancements repo with up to date latest milestone and stage.
• KEP status is marked as implementable.
• KEP has a test plan section filled out.
• KEP has up to date graduation criteria.
• KEP has a production readiness review for the correct stage that has been completed and merged into k/enhancements.

Feel free to file an exception to add this back to the release. If you plan to do so, please file this as early as possible.

Thanks!
/milestone clear

[k8s-triage-robot]

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

This bot triages issues and PRs 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 or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

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

/lifecycle stale

[k8s-triage-robot]

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

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

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

/close

[k8s-ci-robot]

@k8s-triage-robot: Closing this issue.

In response to this:

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

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

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

/close

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.