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 docs for Job managedBy field (alpha) #45132
Conversation
👷 Deploy Preview for kubernetes-io-vnext-staging processing.
|
/retitle [WIP] Add docs for Job managed-by label |
/sig apps |
/milestone 1.30 |
ffd33d4
to
6a03f68
Compare
6a03f68
to
2282582
Compare
2282582
to
47490b8
Compare
/cc @atiratree @alculquicondor |
74af972
to
a804853
Compare
a804853
to
6b1afc2
Compare
/lgtm |
LGTM label has been added. Git tree hash: 8a21e3d23357fd041da2ef0b98a3ca123977e8a3
|
Please review these in detail the [Job API](/docs/reference/kubernetes-api/workload-resources/job-v1/). | ||
We also recommend you running the e2e conformance tests for the Job object to | ||
verify your implementation. |
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.
Please review these in detail the [Job API](/docs/reference/kubernetes-api/workload-resources/job-v1/). | |
We also recommend you running the e2e conformance tests for the Job object to | |
verify your implementation. | |
Please review these in detail in the [Job API](/docs/reference/kubernetes-api/workload-resources/job-v1/). | |
We also recommend that you run the e2e conformance tests for the Job object to | |
verify your implementation. |
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.
Sorry, I was too slow to handle that. @atiratree do you think these are important enough for follow up PR, or just let it stay as is?
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.
@mimowo I would prefer an update if you agree that these formulations sound a bit off. I am not saying my version is the best though, so I will leave the final version up to you..
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 both suggestions are slightly better than original form so let me open the PR, we will see if other folks have other proposals there
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.
Follow up: #45506
I think this is OK to merge, and we welcome further PRs with polish (either for v1.30, or for the move to beta). /approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: sftim The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/milestone 1.30 |
Enhancement tracking: kubernetes/enhancements#4368