Skip to content

docs(k8s): clarify supported kubectl output formats - #88

Open
YamonBot wants to merge 1 commit into
kagent-dev:mainfrom
YamonBot:docs/kubectl-output-formats
Open

YamonBot wants to merge 1 commit into
kagent-dev:mainfrom
YamonBot:docs/kubectl-output-formats

Conversation

@YamonBot

Copy link
Copy Markdown

The k8s_get_resources output description lists only json, yaml and wide, although its handler forwards the string to kubectl -o. Agents can interpret that list as the complete supported set and replace targeted custom-columns requests with larger output.

Clarify the default and include native name, custom-columns=... and jsonpath=... formats, explicitly identifying these as examples rather than an enum. This changes only the tool schema description; command execution and validation remain unchanged.

Validation: make fmt, make lint (0 issues), and make test passed. A deployed caller also successfully used the existing handler with custom-columns to inspect selected runner fields; no new runtime capability is required.

Signed-off-by: YamonBot <141118378+YamonBot@users.noreply.github.com>
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