search

kubernetes / enhancements

Enhancements tracking repo for Kubernetes
Apache License 2.0
3.42k stars 1.47k forks source link

Add job creation timestamp to job annotations #4026

Open helayoty opened 1 year ago

helayoty commented 1 year ago

Enhancement Description

Note: We will release the feature directly in the Beta state since there is no benefit in having an alpha release, as we are simply adding a new annotation which is very little risk (unlike removing an existing one).

helayoty commented 1 year ago

/sig apps /assign

soltysh commented 1 year ago

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

npolshakova commented 1 year ago

Hi @helayoty 👋, Enhancements team here!

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

This enhancement is targeting for stage beta for 1.28 (correct me, if otherwise)

Here's where this enhancement currently stands:

It looks like https://github.com/kubernetes/enhancements/pull/4027 will address some of these issues.

For this KEP, we would just need to update the following:

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!

helayoty commented 1 year ago

For this KEP, we would just need to update the following:

  • Address questions inside the Production Readiness Review Questionnaire

@npolshakova This section requires to have reviewers from the prod-readiness-approvers team which I already added to the reviewers/approvals list.

npolshakova commented 1 year ago

Hi @helayoty, looks like now that the PRR is approved and https://github.com/kubernetes/enhancements/pull/4027 has gone in this enhancement is now tracked for 1.28!

Rishit-dagli commented 1 year ago

Hello @helayoty :wave:, 1.28 Docs Lead here.

Could you 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!

helayoty commented 1 year ago

Hello @helayoty 👋, 1.28 Docs Lead here.

Could you 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!

Hi @Rishit-dagli , PR has been created. https://github.com/kubernetes/website/pull/41857

sftim commented 1 year ago

BTW, there is a typo in the KEP path: https://github.com/kubernetes/enhancements/tree/master/keps/sig-apps/4026-crojob-scheduled-timestamp-annotation

npolshakova commented 1 year ago

Hey again @helayoty :wave:

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

Here’s the enhancement’s state for the upcoming 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!

soltysh commented 1 year ago

@npolshakova all the PRs are listed in the issue description, we try to keep up-to-date, the only one remaining PR is docs https://github.com/kubernetes/website/pull/41857 but that shouldn't block atm.

Atharva-Shinde commented 1 year ago

Hey @helayoty 👋 Enhancements Lead here, With https://github.com/kubernetes/kubernetes/pull/118137 merged as per the issue description, this enhancement is now tracked for v1.28 Code Freeze!

npolshakova commented 1 year ago

/remove-label lead-opted-in

salehsedghpour commented 9 months ago

Hello 👋 1.30 Enhancements Lead here,

I'm closing milestone 1.28 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

atiratree commented 9 months ago

@helayoty are you able to work on graduating this to GA in 1.30?

k8s-triage-robot commented 6 months ago

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

k8s-triage-robot commented 5 months ago

The Kubernetes project currently lacks enough active 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 rotten

helayoty commented 5 months ago

/remove-lifecycle rotten

k8s-triage-robot commented 2 months ago

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

helayoty commented 2 months ago

/remove-lifecycle rotten

soltysh commented 1 month ago

@helayoty any plans to get this GA-ed in 1.32?

soltysh commented 3 weeks ago

/remove-lifecycle stale

soltysh commented 3 weeks ago

I haven't heard from Heba, but I'd like to push this forward especially that it's rather simple feature and comes very handy.

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

shecodesmagic commented 3 weeks ago

Hello @helayoty 👋, v1.32 Enhancements team here.

Just checking in as we approach enhancements freeze on 02:00 UTC Friday 11th October 2024 / 19:00 PDT Thursday 10th October 2024.

This enhancement is targeting for stage stable for v1.32 (correct me, if otherwise)

Here's where this enhancement currently stands:

For this KEP, we would need to update the following:

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!

If you anticipate missing enhancements freeze, you can file an exception request in advance. Thank you!

soltysh commented 3 weeks ago

@shecodesmagic https://github.com/kubernetes/enhancements/pull/4868 should handle all of the above.

shecodesmagic commented 3 weeks ago

@soltysh sounds good. Once that's merged we can mark it as tracked.

shecodesmagic commented 1 week ago

@soltysh Here’s where this enhancement currently stands:

With all the KEP requirements in place and merged into k/enhancements, this enhancement is all good for the upcoming enhancements freeze. 🚀

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

michellengnx commented 1 week ago

Hello @helayoty :wave:, 1.32 Docs Shadow here. Does this enhancement work planned for 1.32 require any new docs or modification to existing docs? If so, please follows the steps here to open a PR against dev-1.32 branch in the k/website repo. This PR can be just a placeholder at this time and must be created before Thursday October 24th 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!

rashansmith commented 1 week ago

Hello @helayoty 👋 from the v1.32 Communications Team! We'd love for you to consider writing a feature blog about your enhancement! Some reasons why you might want to write a blog for this feature include (but are not limited to) if this introduces breaking changes, is important to our users, or has been in progress for a long time and is graduating.

To opt-in, let us know and open a Feature Blog placeholder PR against the website repository by 30th Oct 2024. For more information about writing a blog see the blog contribution guidelines.

michellengnx commented 23 hours ago

Hello @helayoty 👋, 1.32 Docs Shadow here. Does this enhancement work planned for 1.32 require any new docs or modification to existing docs? If so, please follows the steps here to open a PR against dev-1.32 branch in the k/website repo. This PR can be just a placeholder at this time and must be created before Thursday October 24th 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!

Hello @helayoty 👋,

Just a reminder to open a placeholder PR against dev-1.32 branch in the k/website repo for this (steps available here). The deadline for this is 4 days away at Thursday October 24, 2024 18:00 PDT.

Thanks, Michelle