-
Notifications
You must be signed in to change notification settings - Fork 397
rfc: Readiness ttl #2693
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
base: main
Are you sure you want to change the base?
rfc: Readiness ttl #2693
Conversation
Co-authored-by: Jonathan Innis <[email protected]>
Co-authored-by: Jonathan Innis <[email protected]>
Co-authored-by: Jonathan Innis <[email protected]>
Co-authored-by: Jonathan Innis <[email protected]>
This RFC proposes implementing a configurable readiness timeout by leveraging Karpenter's existing node auto repair infrastructure, rather than creating a separate timeout mechanism. Key changes: - Add readinessTTL field to NodePool and NodeClaim specs - Generate dynamic RepairPolicies based on NodeClaim readinessTTL - Reuse existing health controller for readiness timeouts - Automatic 20% safety threshold protection Addresses feedback from PR kubernetes-sigs#1989 to use node auto repair approach. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <[email protected]> Committed-By-Agent: claude
|
Skipping CI for Draft Pull Request. |
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: GnatorX The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
Pull Request Test Coverage Report for Build 19953154884Details
💛 - Coveralls |
Fixes #N/A
Description
How was this change tested?
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.