kubeconfig Validator
Validates a kubectl kubeconfig: required fields, cross-references between clusters, users and contexts, current-context, duplicates and unused entries, server URLs, certificate data and risky settings.
Use the tool
Why this tool exists
A kubeconfig is a YAML file that glues together clusters, users and contexts by name, and a single wrong name gives a vague kubectl error. Merged files from several clouds collect duplicates, unused users and stale contexts. This tool checks the structure: required fields, whether every context points to a cluster and a user that exist, whether current-context is valid, and whether server URLs look right. It also decodes certificate-authority-data and client-certificate-data to confirm the base64 and PEM are sane, notes exec plugins, and warns about risky settings such as insecure-skip-tls-verify and embedded tokens. Credentials are never printed in the report. The file is checked in your browser, so keys are not uploaded.
How to use it
- Paste your kubeconfig YAML into the input box. Remove secrets first if you prefer.
- Run the validation to see errors, warnings and unused entries.
- Fix the listed problems in your file and test with kubectl config view.
Frequently asked questions
What does it check?
Required top-level fields, that clusters, users and contexts have names, that contexts reference existing clusters and users, current-context, duplicate or unused entries, server URLs, and the encoding of certificate data.
Are my credentials shown?
No. Tokens and key data are checked but not printed in the report. Still, avoid pasting live production credentials into any page you do not trust.
What risky settings does it flag?
insecure-skip-tls-verify, tokens embedded in the file, and plain HTTP server URLs. Exec plugins are noted so you remember they depend on the local command being installed.
Does it connect to the cluster?
No. It checks the file only and cannot tell whether the server is reachable or the credentials are accepted.