-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add more granular failure reason for Job PodFailurePolicy #4443
Comments
/sig apps |
/label lead-opted-in |
Hello @danielvegamyhre 👋, 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 Here's where this enhancement currently stands:
For this KEP, we would just want to update the following but it's not required for
The status of this enhancement is marked as |
Hello 👋, 1.30 Enhancements team here. Unfortunately, this enhancement did not meet requirements for enhancements freeze. If you still wish to progress this enhancement in 1.30, please file an exception request. Thanks! |
/milestone clear |
/label lead-opted-in |
Hi @danielvegamyhre 👋 v1.31 Enhancements team here. I wanted to check in as we approach the enhancements freeze on 02:00 UTC Friday 14th June 2024 / 19:00 PDT Thursday 13th June 2024. This enhancement is targeting alpha for v1.31. Please correct me if that isn't the case. Here's where this enhancement currently stands:
For this KEP, we need to do the following:
The status of this enhancement is marked as at risk for enhancement freeze. We can mark it as tracked as soon as the above changes are merged. Please make sure to get this done before the enhancements freeze. If you anticipate missing enhancements freeze, you can file an exception request in advance. Let me know if you have any questions! Thank you! |
Hello @danielvegamyhre 👋, 1.31 Docs Shadow here. Does the work related to this KEP planned for 1.31 require any new docs or modification to existing docs? If so, please follows the steps here to open a PR against dev-1.31 branch in the k/website repo. This PR can be just a placeholder at this time and must be created before Thursday June 27, 2024 18:00 PDT. Also, take a look at Documenting for a release to get yourself familiarised with the docs requirement for the release. Thank you! |
With #4479 merged, we can mark this KEP as |
Hello there @danielvegamyhre 👋 from the v1.31 Communications Team! 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 Edit: @danielvegamyhre can you assign this issue to yourself? So it's easier to check the owner on the GitHub project. |
Hello @danielvegamyhre 👋, 1.31 Docs Lead here. |
Reminder of the 3rd of July deadline! |
Added placeholder PR kubernetes/kubernetes#125804 |
Hey again @danielvegamyhre 👋 Kubernetes 1.31 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:
For this enhancement, it looks like the following PRs are open and need to be merged before code freeze (and we need to update the Issue description to include all the related PRs of this KEP):
If you anticipate missing code freeze, you can file an [exception request](https://github.com/kubernetes/sig-release/blob/master/releases/EXCEPTIONS.md) in advance. Also, please let me know if there are other PRs in As always, we are here to help if any questions come up. Thanks! The status of this enhancement is marked as |
Hey @danielvegamyhre 👋 Kubernetes 1.31 Enhancements team here. Following up on the message above as we approach code freeze at 02:00 UTC Wednesday 24th July 2024 / 19:00 PDT Tuesday 23rd July 2024. Please let me know if you have any questions. |
Hello @danielvegamyhre 👋 Kubernetes 1.31 Enhancements team here, Unfortunately, the implementation (code related) PR(s) associated with this enhancement is not in the merge-ready state by code-freeze and hence this enhancement is now removed from the v1.31 milestone. If you still wish to progress this enhancement in v1.31, please file an exception request as soon as possible, within three days. If you have any questions, you can reach out in the #release-enhancements channel on Slack and we'll be happy to help. Thanks! |
/milestone clear |
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 |
The Kubernetes project currently lacks enough contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
/remove-lifecycle stale |
@tenzen-y @danielvegamyhre are you planning any work on this enhancement in 1.33? |
AFAIK, @danielvegamyhre is still working on implementations at kubernetes/kubernetes#125804 |
I don't have any plans to continue work on this at the moment |
Enhancement Description
Reason
field to the JobPodFailurePolicyRule
, which allows the user to specify the failure reason which will be included in the condition added to the Job when it fails.k/enhancements
) update PR(s): KEP-4443: Add more granular Job failure reason for PodFailurePolicy #4479k/k
) update PR(s):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.
The text was updated successfully, but these errors were encountered: