Skip to content

feat: Return unexpected kubectl-ai errors in RunOnce mode, display them in k8s-bench#594

Merged
droot merged 1 commit into
GoogleCloudPlatform:mainfrom
noahlwest:tool-errors
Oct 22, 2025
Merged

feat: Return unexpected kubectl-ai errors in RunOnce mode, display them in k8s-bench#594
droot merged 1 commit into
GoogleCloudPlatform:mainfrom
noahlwest:tool-errors

Conversation

@noahlwest
Copy link
Copy Markdown
Collaborator

@noahlwest noahlwest commented Oct 22, 2025

  • kubectl-ai returns unexpected errors encountered in kubectl-ai RunOnce mode
  • k8s-bench run now counts unexpected errors as errors instead of failures
  • k8s-bench analyze now accounts for errors encountered

Tested this with local served gpt-oss-20b, errors like 404, 400, tool parsing errors, etc. are saved and recorded as errors now in k8s-bench. Easiest way to reliably recreate errors is to use start a vllm instance and point to a model that doesn't exist, or use a model with known issues (like gpt-oss-20b on completions endpoint.)

  • When unexpected error is encountered and returned to k8s-bench, we print usage/help text for kubectl-ai. This adds a little bit of noise to the logs but we can fix that in a later pr

@droot
Copy link
Copy Markdown
Member

droot commented Oct 22, 2025

Thank you so much for quick turn around on this one. This addresses a critical issues.

@droot droot merged commit 17b3234 into GoogleCloudPlatform:main Oct 22, 2025
7 checks passed
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.

2 participants