-
Notifications
You must be signed in to change notification settings - Fork 14.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
GA TTLAfterFinished #30031
GA TTLAfterFinished #30031
Conversation
👷 Deploy Preview for kubernetes-io-vnext-staging processing. 🔨 Explore the source changes: 1111731 🔍 Inspect the deploy log: https://app.netlify.com/sites/kubernetes-io-vnext-staging/deploys/616fa008c2bc9400070e0164 |
/milestone 1.23 |
@sahilvv: You must be a member of the kubernetes/website-milestone-maintainers GitHub team to set the milestone. If you believe you should be able to issue the /milestone command, please contact your Website milestone maintainers and have them propose you as an additional delegate for this responsibility. In response to this:
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/test-infra repository. |
/sig apps |
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 OK to merge.
Ideally, we should improve this document as well for general availability. I'd reword “The TTL controller only supports Jobs for now” given that we now have a stable definition of what the control plane does.
The comment about NTP could change to be generic over which time sync technology you use.
Nice to have: follow the style guide throughout.
/lgtm
LGTM label has been added. Git tree hash: 318aa2e2edfe12b5e7e42d991813358ffb519776
|
/assign @chrisnegus |
+1, I don't think the docs should be speculating about the future now that this is a GA feature. |
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.
/lgtm
- I have a suggested rewording for the overview
- Same as GA TTLAfterFinished #30031 (review): I'd prefer to change “NTP” to mention time sync (you could use another mechanism).
@@ -8,23 +8,17 @@ weight: 70 | |||
|
|||
<!-- overview --> | |||
|
|||
{{< feature-state for_k8s_version="v1.21" state="beta" >}} | |||
{{< feature-state for_k8s_version="v1.23" state="stable" >}} | |||
|
|||
The TTL controller provides a TTL (time to live) mechanism to limit the lifetime of resource |
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.
For GA, I would prefer to rename this to “The TTL-after-finished controller”
for example:
The TTL controller provides a TTL (time to live) mechanism to limit the lifetime of resource | |
The TTL-after-finished {{<glossary_tooltip text="controller" term_id="controller">}} provides | |
a TTL (time to live) mechanism to limit the lifetime of Kubernetes workload |
LGTM label has been added. Git tree hash: bb56aa35a71e4393363cf06e1af068b5dfb073f3
|
I also recommend looking at #26917, which is about making sure the right pages hyperlink to the TTLAfterFinished docs. |
@sftim I have addressed the review feedback given so far. Please take a look. Thanks again! |
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.
Yep, still LGTM. Also happy to see tweaks. But bear in mind we can merge this and do the tweaks in a different PR; that works fine too!
Question: should we also retitle the page?
For example, to “Automatic Clean-up for Finished Jobs”.
/lgtm
determine whether the TTL has expired or not, this feature is sensitive to time | ||
skew in the cluster, which may cause TTL controller to clean up resource objects | ||
at the wrong time. | ||
|
||
In Kubernetes, it's required to run NTP on all nodes | ||
In Kubernetes, it's required to run a time sync solution on all nodes | ||
(see [#6159](https://github.com/kubernetes/kubernetes/issues/6159#issuecomment-93844058)) |
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.
nit: I'd omit this line.
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.
removed @sftim.
LGTM label has been added. Git tree hash: d699732a280fe69dc12b7e727de016ec23b16c0d
|
@chrisnegus @ahg-g @janetkuo please review. |
|
||
The TTL controller only supports Jobs for now. A cluster operator can use this feature to clean | ||
The TTL-after-finished controller is only supported for Jobs. A cluster operator can use this feature to clean |
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.
It we change this, we should also change other references of "resources" to "Jobs".
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.
Great comment @janetkuo. I have updated the references of resources
to jobs
.
Still LGTM. Also happy to see tweaks. But bear in mind we can merge this and do the tweaks in a different PR; that works fine too! /lgtm |
LGTM label has been added. Git tree hash: 6208ac93ca2cf582c8e9e68bcfb2366d943da74f
|
@janetkuo could you please re-review and approve if changes look good. |
@sftim can you grant me /approve on this. |
I'll leave approval to the SIG Release Docs folks. |
@mehabhalodiya @chrisnegus Please review. |
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: janetkuo, reylejano 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 |
@sftim @reylejano Thanks for taking care of this. |
This PR updates the TTLAfterFinish controller to stable as part of 1.23 k8s release.
Related PRs: