Skip to content

fix(controller): populate Harness status - #2876

Open
yashrajshuklaaa wants to merge 1 commit into
kagent-dev:mainfrom
yashrajshuklaaa:fix/harness-status
Open

yashrajshuklaaa wants to merge 1 commit into
kagent-dev:mainfrom
yashrajshuklaaa:fix/harness-status

Conversation

@yashrajshuklaaa

@yashrajshuklaaa yashrajshuklaaa commented Sep 18, 2026

Copy link
Copy Markdown
Contributor

This adds controller reconciliation for Harness.status which was previously never populated. It sets the Ready condition based on whether the referenced WorkerPool exists. Also adds tests for the ready and missing WorkerPool cases.
Controller tests are passing.
Fixes #2764

@yashrajshuklaaa
yashrajshuklaaa requested a review from a team as a code owner September 18, 2026 19:04
@github-actions github-actions Bot added bug Something isn't working and removed bug Something isn't working labels Sep 18, 2026
@yashrajshuklaaa

Copy link
Copy Markdown
Contributor Author

@EItanya PTAL

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

Labels

bug Something isn't working

Projects

None yet

Development

Successfully merging this pull request may close these issues.

HarnessStatus is never populated: a Harness has no status subresource and status.capabilities is unreadable

1 participant