Kubeconfig sanitizer
Strip secrets from a kubeconfig before sharing it.
Loading the tool…
What it does, how to use it, and questions
What it does
Kubeconfigs embed cluster APIs plus user credentials (token, client-key-data, certificate data). Sharing one raw is a credential leak.
This sanitizer removes secret fields and lists what was stripped so you can share cluster names safely.
How to use it
- Paste a kubeconfig YAML.
- Download the sanitized copy.
- Confirm the removed-keys list.
Things to watch for
- Exec plugin configs may still point at local credential helpers. Review the YAML.
- Sanitized configs cannot authenticate.
Questions
- Is the kubeconfig uploaded?
- No.
- What is removed?
- Tokens, passwords, client-key-data, client-certificate-data and similar secret keys.
- Can I re-add a key?
- Use a fresh credential from your cloud or cluster admin.
- Does it talk to the cluster?
- No.