kubectl delete: Add interactive(-i) flag

[ardaguclu]

Enhancement Description

• One-line enhancement description (can be used as a release note): Add interactive(-i) flag to kubectl delete command that will ask confirmation to user to proceed
• Kubernetes Enhancement Proposal: https://github.com/kubernetes/enhancements/blob/master/keps/sig-cli/3895-kubectl-delete-interactivity/README.md
• Discussion Link: sig-cli February 22, 2023 bi-weekly, comment
• Primary contact (assignee): @ardaguclu
• Responsible SIGs: sig-cli
• Enhancement target (which target equals to which milestone):
  • Alpha release target (x.y): 1.28
  • Beta release target (x.y): 1.29
  • Stable release target (x.y):
• Alpha
  • KEP (k/enhancements) update PR(s): KEP-3895: kubectl delete: Add interactive(-i) flag #3896
  • Code (k/k) update PR(s): kubectl delete: Introduce new interactive flag for interactive deletion kubernetes#114530
  • Docs (k/website) update PR(s): document kubectl delete --interactive flag website#41979
• Beta
  • KEP (k/enhancements) update PR(s): KEP-3895: Promote interactive flag in delete command to beta #4178
  • Code (k/k) update PR(s): KEP-3895: Promote interactive delete to beta kubernetes#120416
  • Docs (k/website) update(s): Remove alpha environment variable because feature is in beta website#42907
• Stable
  • KEP (k/enhancements) update PR(s): KEP-3895: Promote interactive delete to stable #4396
  • Code (k/k) update PR(s): Add e2e test for kubectl interactive delete kubernetes#122653
  • Docs (k/website) update(s):

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

[ardaguclu]

/sig cli
/assign

[soltysh]

/milestone v1.28
/label lead-opted-in

[soltysh]

/stage alpha

[Kasambx]

Hello @ardaguclu 👋, Enhancements team here.

Just checking in as we approach enhancements freeze on 1:00 UTC on Friday 16th June 2023..

This enhancement is targeting for stage alpha for v1.28 (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.28
• KEP readme has a updated detailed test plan section filled out
• KEP readme has up to date graduation criteria
• KEP has a production readiness review that has been completed and merged into k/enhancements.

For this KEP, we would just need to update the following:
-Ensure that the PRs are merged.

The status of this enhancement is marked as at risk. Please keep the issue description up-to-date with appropriate stages as well. Thank you!

[taniaduggal]

Hello @ardaguclu 1.28 Docs Shadow here.

Does this enhancement work planned for 1.28 require any new docs or modification to existing docs?

If so, please follows the steps here to open a PR against dev-1.28 branch in the k/website repo. This PR can be just a placeholder at this time and must be created before Thursday 20th July 2023.

Also, take a look at Documenting for a release to get yourself familiarize with the docs requirement for the release.

Thank you!

[Atharva-Shinde]

Hey @ardaguclu Enhancements team here 👋

Just checking in as we approach Code freeze at 01:00 UTC Wednesday, 19th July 2023 .

Here’s the enhancement’s state for the upcoming code freeze:

• All the PRs that are related to your enhancement are linked in the above issue description (for tracking purposes). This includes code, tests, and documentation related PR/s.
• All code related PR/s are merged or are in merge-ready state ( i.e they have approved and lgtm labels applied) by the code freeze deadline. This includes any tests related PR/s too.

This is the code related PR that I found on this KEP issue

• kubectl delete: Introduce new interactive flag for interactive deletion kubernetes#114530

Please keep the issue description up-to-date with all the PR/s that are associated with this KEP and let me know if there are other PR/s in k/k we should be tracking for this KEP.

As always, we are here to help if any questions come up. Thanks!

[Atharva-Shinde]

Hey @ardaguclu 👋 Enhancements Lead here,
With kubernetes/kubernetes#114530 merged as per the issue description, this enhancement is now tracked for v1.28 Code Freeze!

[npolshakova]

Hello 👋, 1.29 Enhancements Lead here.

If you wish to progress this enhancement in v1.29, please have the SIG lead opt-in your enhancement by adding the lead-opt-in and milestone v1.29 labels before the Production Readiness Review Freeze.

/remove-label lead-opted-in

[sreeram-venkitesh]

Hey again @ardaguclu 👋 v1.29 Enhancements team here,

Just checking in as we approach code freeze at 01:00 UTC Wednesday 1st November 2023 .

Here's where this enhancement currently stands:

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

For this KEP, the following PR has been merged before the code freeze:

• KEP-3895: Promote interactive delete to beta kubernetes#120416

With the PR merged and the issue description updated, this KEP is currently tracked for code freeze. 🎉

As always, we are here to help if any questions come up. Thanks!

[a-mccarthy]

hi @ardaguclu, 👋 from the v1.29 Release Team-Communications! We would like to check if you have any plans to publish a blog for this KEP regarding new features, removals, and deprecations for this release.

If so, you need to open a PR placeholder in the website repository.
The deadline will be on Tuesday 14th November 2023 (after the Docs deadline PR ready for review)

Here is the 1.29 calendar

[salehsedghpour]

/remove-label lead-opted-in

[salehsedghpour]

Hello 👋 1.30 Enhancements Lead here,

I'm closing milestone 1.29 now,
If you wish to progress this enhancement in v1.30, please follow the instructions here to opt in the enhancement and make sure the lead-opted-in label is set so it can get added to the tracking board and finally add /milestone v1.30. Thanks!

/milestone clear

[soltysh]

/label lead-opted-in
/milestone v1.30
/stage stable

[meganwolf0]

Hello @ardaguclu 👋, Enhancements team here.

Just checking in as we approach enhancements freeze on 02:00 UTC Friday 9th February 2024.

This enhancement is targeting for stage stable for 1.30 (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: 1.30. KEPs targeting stable will need to be marked as implemented after code PRs are merged and the feature gates are removed.
• KEP readme has up-to-date graduation criteria
• 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 just need to update the following:

• Update the latest-milestone and stage in kep.yaml
• Update the PRR for stable

The status of this enhancement is marked as at risk for enhancement freeze. Please keep the issue description up-to-date with appropriate stages as well. Thank you!

[ardaguclu]

Thanks @meganwolf0, updated the KEP status to implemented.

[meganwolf0]

With all the requirements fulfilled this enhancement is now marked as tracked for the upcoming enhancements freeze 🚀

[natalisucks]

Hi @ardaguclu,

👋 from the v1.30 Communications Team! We'd love for you to opt in to write a feature blog about your enhancement!

We encourage blogs for features including, but not limited to: breaking changes, features and changes important to our users, and features that have been in progress for a long time and are graduating.

To opt in, you need to open a Feature Blog placeholder PR against the website repository.
The placeholder PR deadline is 27th February, 2024.

Here's the 1.30 Release Calendar

[Vyom-Yadav]

Hello @ardaguclu 👋, v1.30 Docs Shadow here.

Does this enhancement work planned for v1.30 require any new docs or modification to existing docs?

If so, please follows the steps here to open a PR against dev-1.30 branch in the k/website repo. This PR can be just a placeholder at this time and must be created before Thursday, February 22nd, 2024 18:00 PDT

Also, take a look at Documenting for a release to get yourself familiarize with the docs requirement for the release.

Thank you!

---

Does this enhancement work planned for v1.30 require any new docs or modification to existing docs?

We'll need a stability version bumping PR at a minimum, marking it as Need Docs. Thanks!
Update we don't need docs for this, marking as Has Docs

[meganwolf0]

Hey again @ardaguclu 👋 Enhancements team here,

Just checking in as we approach code freeze at 02:00 UTC Wednesday 6th March 2024 .

Here's where this enhancement currently stands:

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

For this enhancement, it looks like the following PRs are open and need to be merged before code freeze:

• Add e2e test for kubectl interactive delete kubernetes#122653

With this, it is now marked as at risk for code freeze for the v1.30 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!

[meganwolf0]

Hello @ardaguclu 👋, Enhancements team here.

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

• Add e2e test for kubectl interactive delete kubernetes#122653

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

[ardaguclu]

I think, we can close this issue as completed as it has been promoted to stable in 1.30.