Kubernetes Tools
Inspect, diff, and split Kubernetes YAML. We do not talk to your cluster or read kubeconfig.
5 tools · 100% browser-based · No uploads · No signup
About these Kubernetes tools
Kubernetes tools inspect manifests, diff resources, split multi-document YAML, sketch a Helm chart from YAML, and check apiVersion deprecations for a target cluster version. They do not talk to your cluster. No kubeconfig is uploaded.
Use them on a train or in a browser when installing kubectl plugins is not worth it. Apply and dry-run still belong on a machine with credentials. API deprecation data is a snapshot; confirm against the Kubernetes version you actually run.
Tools in this category
K8s Inspector
Inspect Kubernetes manifests: detect resource types and check required fields.
K8s Resource Diff
Compare Kubernetes manifests with a semantic diff of added, removed, and changed resources.
K8s Manifest Splitter
Split a multi-document YAML file into separate manifests and download them as a ZIP.
K8s to Helm
Turn Kubernetes manifests into a Helm chart with generated values and templates.
K8s API Checker
Check manifests for deprecated or removed Kubernetes APIs by cluster version.
How these tools run in your browser
Manifests are parsed as YAML documents. Inspector looks at apiVersion, kind, and metadata. Diff is resource-aware when names match. Helm export templatizes obvious values; it will not produce a chart you should ship without review. API checker compares against a built-in deprecation table.
Common Use Cases
- See kind, name, and missing required fields in a pasted manifest
- Compare two Deployment YAML files after a change
- Split a single file with --- into one file per resource
- Get a head start on Helm values from existing YAML
- Check whether networking.k8s.io/v1beta1 still exists on 1.25+
Common Mistakes
Frequently Asked Questions
No. It is a quick inspect. Use kubectl explain and the official docs for field-level schema.
No. There is no API server call from these pages.
Pick the version in the API checker UI. When in doubt, match kubectl version on the cluster, not your laptop.