Skip to content

Design: [Mirror #1144] [Mirror] Expected Runtime Plugin for Soft Eviction via Requeue Action#1145

Draft
omer-dayan wants to merge 1 commit intomainfrom
bridge/shadow-pr-60
Draft

Design: [Mirror #1144] [Mirror] Expected Runtime Plugin for Soft Eviction via Requeue Action#1145
omer-dayan wants to merge 1 commit intomainfrom
bridge/shadow-pr-60

Conversation

@omer-dayan
Copy link
Collaborator

Propagated from shadow repo
Shadow PR: omer-dayan/KAI-Scheduler#60


Design Document

This PR adds an architectural design document for the feature requested in #59.

Design File: docs/developer/designs/59-expected-runtime-plugin.md

Review Checklist

Please review the design document for:

  • Problem statement is clear and concise
  • Goals and non-goals are well-defined
  • API changes follow Kubernetes conventions (if applicable)
  • Examples are concrete and cover key scenarios
  • Test strategy is comprehensive
  • Backward compatibility is maintained or migration path is documented
  • Risks are identified with mitigations
  • Design follows existing project patterns

⚠️ Validation Report

Quality Score: 45.0/100

Errors: 3
Warnings: 4

View Full Report

Design Document Validation Report

Status: ❌ FAILED
Quality Score: 45.0/100
Issues Found: 7

❌ Errors (Must Fix)

1. Required section 'Proposal' is missing

Category: completeness
Suggestion: Add a '## Proposal' section to the document

2. Required section 'Design Details' is missing

Category: completeness
Suggestion: Add a '## Design Details' section to the document

3. Required section 'Test Plan' is missing

Category: completeness
Suggestion: Add a '## Test Plan' section to the document

⚠️ Warnings (Should Fix)

1. Recommended section 'Graduation Criteria' is missing

Category: completeness
Suggestion: Consider adding a '## Graduation Criteria' section

2. API changes detected but no validation tags found

Category: content
Suggestion: Add kubebuilder validation tags (e.g., +kubebuilder:validation:Required)

3. Heading hierarchy jump (level 1 to 3)

Line: 649
Category: formatting
Suggestion: Use incremental heading levels (don't skip levels)

4. Heading hierarchy jump (level 1 to 3)

Line: 690
Category: formatting
Suggestion: Use incremental heading levels (don't skip levels)

Related Issue: #59


Designed by KAI Agent

@coderabbitai
Copy link
Contributor

coderabbitai bot commented Mar 5, 2026

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 9f086ba2-d2b3-4801-a81c-7cc687e80aee

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch bridge/shadow-pr-60

Tip

Try Coding Plans. Let us write the prompt for your AI agent so you can ship faster (with fewer bugs).
Share your feedback on Discord.


Comment @coderabbitai help to get the list of available commands and usage tips.

- Promote `expectedRuntime` and `requeueDelay` to `PodGroup.spec` fields (with annotation backward compatibility shim).
- Annotations remain supported as overrides for compatibility.
- Add kubebuilder validation tags for all new spec fields.
- Finalize naming of annotation keys (remove TBDs).
Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Remove TBDs?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant