/sig apps
/wg batch

/assign

/assign

/sig scheduling
/sig api-machinery

Hello @alculquicondor 👋, 1.25 Enhancements team here.

Just checking in as we approach enhancements freeze on 18:00 PT on Thursday June 23, 2022, which is just over 2 days from now.

For note, This enhancement is targeting for stage alpha for 1.25 (correct me, if otherwise)

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
• KEP has a updated detailed test plan section filled out
• KEP has up to date graduation criteria
• KEP has a production readiness review that has been completed and merged into k/enhancements.

The open PR #3374 is addressing all the listed criteria above. We would just require getting it merged by the Enhancements Freeze.

For note, 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!

With KEP PR #3374 merged, the enhancement is ready for the 1.25 Enhancements Freeze.

For note, the status is now marked as tracked. Thank you so much!

Hello @alculquicondor 👋, 1.25 Release Docs Lead here.
This enhancement is marked as ‘Needs Docs’ for 1.25 release.

Please follow the steps detailed in the documentation to open a PR against dev-1.25 branch in the k/website repo. This PR can be just a placeholder at this time, and must be created by August 4.
 Also, take a look at Documenting for a release to familiarize yourself with the docs requirement for the release.

Thank you!

Hi @alculquicondor @mimowo, Enhancements team here again 👋

Checking in as we approach Code Freeze at 01:00 UTC on Wednesday, 3rd August 2022.

Please ensure that the following items are completed before the code-freeze:

• All PRs to the Kubernetes repo that are related to your enhancement are linked in the above issue description (for tracking purposes).
  Refactor gc_controller to do not use the deletePod stub kubernetes#111070
  Refactor taint_manager to do not use getPod and getNode stubs kubernetes#111084
  Add integration test for podgc kubernetes#111091
  Append new pod conditions when deleting pods to indicate the reason for pod deletion kubernetes#110959
  Support handling of pod failures with respect to the configured rules kubernetes#111113
  Add worker to clean up stale DisruptionTarget condition kubernetes#111475
• All PRs are fully merged by the code freeze deadline.
  Append new pod conditions when deleting pods to indicate the reason for pod deletion kubernetes#110959
  Support handling of pod failures with respect to the configured rules kubernetes#111113
  Add worker to clean up stale DisruptionTarget condition kubernetes#111475

Let me know if there are any additional k/k PRs besides the ones listed above

Currently, the status of the enhancement is marked as at-risk

Thanks :)

@Atharva-Shinde @alculquicondor there is one more PR that should be included before the code freeze: kubernetes/kubernetes#111475

With all PRs to k/k merged, this KEP is now tracked for code freeze!

@mimowo Look like kubernetes/kubernetes#126169 has tests related to this KEP. Please make sure to get it merged before the test freeze deadline (01:00 UTC Wednesday 31st July 2024 / 19:00 PDT Tuesday 30th July 2024).

@mimowo Look like kubernetes/kubernetes#126169 has tests related to this KEP. Please make sure to get it merged before the test freeze deadline (01:00 UTC Wednesday 31st July 2024 / 19:00 PDT Tuesday 30th July 2024).

@sreeram-venkitesh thanks for reaching out, I have updated the PR and will try to merge it, but OTOH I don't think it is required for this release cycle, because we will not promote these tests in this cycle anyway (per kubernetes/kubernetes#125482 (comment)). We have promoted already 2 tests which didn't have the flakiness issue: kubernetes/kubernetes#125482

Just a friendly reminder: if you need to open a Feature Blog placeholder PR against the website repository, please go ahead and do so. If you have any questions or need any help, feel free to reach out! For more information about writing a blog, check out the blog contribution guidelines.

@edithturn I was busy preparing the code updates for the release cycle and missed this message, but I have already opened the placeholder PR for the blog-post, see #3329 (comment), and I'm working on the content. Can we still include it?

@mimowo @alculquicondor Can we close this issue since the feature is stable?

There are some post GA tasks to complete https://github.com/kubernetes/enhancements/tree/master/keps/sig-apps/3329-retriable-and-non-retriable-failures#deprecation

@alculquicondor in preparation for the next release, could you give me an ETA for when you expect the post GA tasks to complete? Do we need to track this KEP in the next cycle?

The only pending work is to remove the feature-gate in 1.33.

I think we can close the issue, I see that other issues corresponding to GA features which are pending feature-gate removal are already closed, examples: AdmissionWebhookMatchConditions, AggregatedDiscoveryEndpoint, APIListChunking.

It might be confusing that we have the "Modify the code to ignore the PodDisruptionConditions and JobPodFailurePolicy feature gates" to reflect the actual state" task in the Deprecation, but it was already done. I have created the KEP update: #4835. @alculquicondor please add these two PRs to the implementation list in the issue: kubernetes/kubernetes#125994 and kubernetes/kubernetes#126102

Added

Closing the issue seems ok, given the precedent of other KEPs that already graduated.

/close

@mimowo: Closing this issue.

/remove-label lead-opted-in
/remove-label tracked/yes