docs: add reason-aware repair policy matching RFC

[sebpalmerio]

Description

This PR adds a design RFC (designs/reason-aware-repair-policy-matching.md) defining reason-aware repair policy matching and eligibility for Karpenter Node Repair.

Problem

Node Repair currently maps a NodeCondition type and status to one toleration before replacing the Node. The reboot proposal adds another repair action, so diagnoses reported under the same condition may require different confidence delays, drain limits, and responses. Provider rules may also overlap and become eligible at different times. Matching must resolve those rules deterministically without relying on policy order or in-memory state.

Proposal

Extend the provider-supplied RepairPolicy with ReasonRegex and Action, then:

• Match stable NodeCondition.reason values with Go regular expressions.
• Require a condition-level replacement fallback for compatibility with newly introduced reasons.
• Evaluate overlapping policies independently and merge eligible behavior using fixed action, termination grace period, and eligibility rules.
• Derive eligibility from lastTransitionTime and reconstruct it from current API state after restart.
• Validate the complete provider policy set before registering Node Repair.

Related RFCs

• Voluntary node repair #3192
• Reboot as a Node action #3259
• Original Node Repair design #1768

How was this change tested?

N/A — documentation/design only.

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

LLMs were used in the writing of this document, but the contribution is mine.

[linux-foundation-easycla]

The committers listed above are authorized under a signed CLA.

• ✅ login: sebpalmerio / name: Sebestien Palmerio (ea18c54)

[kubernetes-prow]

Welcome @sebpalmerio!

It looks like this is your first PR to kubernetes-sigs/karpenter 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.

You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.

You can also check if kubernetes-sigs/karpenter has its own contribution guidelines.

You may want to refer to our testing guide if you run into trouble with your tests not passing.

If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!

Thank you, and welcome to Kubernetes. 😃

[kubernetes-prow]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: sebpalmerio
Once this PR has been reviewed and has the lgtm label, please assign njtran for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment