-
Notifications
You must be signed in to change notification settings - Fork 15.1k
Add batch.kubernetes.io/cronjob-scheduled-timestamp annotation information to cronjob page #48498
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
Conversation
👷 Deploy Preview for kubernetes-io-vnext-staging processing.
|
✅ Pull request preview available for checkingBuilt without sensitive environment variables
To edit notification comments on pull requests, go to your Netlify site configuration. |
|
/sig apps |
| The CronJob is only responsible for creating Jobs that match its schedule, and | ||
| the Job in turn is responsible for the management of the Pods it represents. | ||
|
|
||
| Starting with Kubernetes v1.32 the job created by CronJob controller will have an annotation `batch.kubernetes.io/cronjob-scheduled-timestamp` which will show the original (expected) creation timestamp for a Job. The value of this field is in RFC3339 format. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is not technically true. Wouldn't this annotation have shown up in 1.28 and now we are forbidding users from turning it off in 1.32?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Technically - yes, it should show up starting in 1.32, but since it was beta, it could potentially be disabled. Going with 1.32, where the feature is always on is safer assumption, b/c it will always appear. I thought for a while to go with 1.28, but based on what I wrote, I've decided to go with the stable.
|
@soltysh if you're ready for more reviews, feel free to mark this as not-draft |
@sftim yup, it's ready for final review /assign @atiratree |
| The CronJob is only responsible for creating Jobs that match its schedule, and | ||
| the Job in turn is responsible for the management of the Pods it represents. | ||
|
|
||
| Starting with Kubernetes v1.32 the job created by CronJob controller will have an annotation `batch.kubernetes.io/cronjob-scheduled-timestamp` which will show the original (expected) creation timestamp for a Job. The value of this field is in RFC3339 format. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think it is a bit confusing to place this after:
The CronJob is only responsible for creating Jobs that match its schedule, and
the Job in turn is responsible for the management of the Pods it represents.
Can we either:
- highlight here why this annotation is useful? For example:
can be useful if the job has not been created according to the schedule - or just place above the last sentence or somewhere else in the Job creation section?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good point, moved it up, after the first paragraph.
…ation to cronjob page Signed-off-by: Maciej Szulik <soltysh@gmail.com>
95087fb to
a4e093c
Compare
|
LGTM from sig-apps POV |
|
Tech LGTM noted, @tengqm could we get your docs review for this one? |
| Kubernetes tries to avoid those situations, but does not completely prevent them. Therefore, | ||
| the Jobs that you define should be _idempotent_. | ||
|
|
||
| Starting with Kubernetes v1.32 the job created by CronJob controller will have an annotation |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
v1.32 will be out when this documentation merges, so this should be in present tense.
Consider this non-blocking if necessary.
| Starting with Kubernetes v1.32 the job created by CronJob controller will have an annotation | |
| Starting with Kubernetes v1.32, the job created by CronJob controller has an annotation |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Suggest: job --> Job
| Kubernetes tries to avoid those situations, but does not completely prevent them. Therefore, | ||
| the Jobs that you define should be _idempotent_. | ||
|
|
||
| Starting with Kubernetes v1.32 the job created by CronJob controller will have an annotation |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Suggest: job --> Job
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: janetkuo The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
This is superseded by #48860 |
|
PR needs rebase. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
Description
Add batch.kubernetes.io/cronjob-scheduled-timestamp annotation information to cronjob page
Issue
kubernetes/enhancements#4026