Add job creation timestamp to job annotations

[helayoty]

Enhancement Description

• One-line enhancement description (can be used as a release note): Add new annotation JobCreationTimestampAnnotation to the batch API.
• Kubernetes Enhancement Proposal:
• Discussion Link: Inject schedule name into newly created job kubernetes#108609
• Primary contact (assignee): @helayoty
• Responsible SIGs: sig-apps
• Enhancement target (which target equals to which milestone):
  • Alpha release target (x.y): N/A
  • Beta release target (x.y): 1.28
  • Stable release target (x.y):

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).

• Beta
  • KEP (k/enhancements) update PR(s): KEP-4026: Add new annotation for job creation timestamp #4027
  • Code (k/k) update PR(s): feat: Append job creation timestamp to cronjob annotations kubernetes#118137
  • Docs
    • Update k/website on the dev-1.28 branch PR(s): Update docs with the new Job annotation website#41857
• Stable
  • KEP (k/enhancements) update PR(s):
  • Code (k/k) update PR(s):
  • Docs (k/website) update(s):

[helayoty]

/sig apps
/assign

[soltysh]

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

[npolshakova]

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:

• KEP readme using the latest template has been merged into the k/enhancements repo.
• KEP status is marked as implementable for latest-milestone: 1.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.

It looks like #4027 will address some of these issues.

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

• Address questions inside the Production Readiness Review Questionnaire

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]

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]

Hi @helayoty, looks like now that the PRR is approved and #4027 has gone in this enhancement is now tracked for 1.28!

[Rishit-dagli]

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!

[helayoty]

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. kubernetes/website#41857

[sftim]

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]

Hey again @helayoty 👋

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:

• 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.
  • feat: Append job creation timestamp to cronjob annotations kubernetes#118137

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]

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

[Atharva-Shinde]

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

[npolshakova]

/remove-label lead-opted-in