Skip to main content
Version: v0.2.0

FAQ

Does kubediag mutate cluster resources?

No. triage is read-only. It inspects cluster state and emits findings, evidence, and follow-up commands.

Is kubediag a kubectl plugin or a standalone CLI?

Both. The same binary works as triage and as kubectl-kubediag.

Does kubediag replace kubectl?

No. It narrows the search space and tells you which kubectl commands are most useful next.

How does kubediag rank findings?

Findings are ranked by severity and confidence, with ties broken consistently by rule metadata. The goal is to show the most incident-driving diagnosis first.

Does kubediag support machine-readable output?

Yes. Use -o json for automation and -o markdown or kubediag report namespace for report writing.

Why are there rule IDs?

Rule IDs are public, stable identifiers that teams can reference in runbooks, alerts, and automation.

What happens if RBAC blocks some resources?

kubediag emits an informational access finding explaining that the diagnosis may be incomplete rather than fabricating certainty.

Can I use kubediag in CI or incident bots?

Yes. The JSON output, stable IDs, and meaningful exit codes are designed for that style of integration.