K8s Resource Diff
Kubernetes manifest diff online free. Compare K8s YAML files with semantic diff. See added, removed, changed resources—K8s diff checker.
Original / Local
Modified / Remote
Paste two K8s manifests to compare
Features
- Side-by-side visual diff of two Kubernetes YAML manifests
- Semantic diff: ignores formatting, compares parsed YAML structure
- Highlights added (green), removed (red), and changed (yellow) fields
- Key path display for nested changes (e.g., <code>spec.containers[0].image</code>)
- Support for multi-document YAML files
- Copy diff output in unified diff format
Common Use Cases
- Compare manifests before and after an image or version upgrade
- Review infrastructure-as-code changes before applying to production
- Audit what changed between two Helm release revisions
- Understand the difference between dev, staging, and prod manifest versions
- Debug unexpected behavior by comparing the running state vs. desired state
Kubernetes Manifest Diffing
Kubernetes manifests describe the desired state of your cluster resources. As applications evolve, manifests change — new images, updated resource limits, additional environment variables, changed replicas. Diffing lets you review those changes before applying them.
A semantic diff (comparing parsed YAML structures) is preferable to a textual diff for Kubernetes manifests because it highlights logical changes (field value changes, added/removed keys) without flagging cosmetic differences like extra whitespace or comment changes.
kubectl diff -f manifest.yaml performs a live diff against the cluster state — useful in production. This tool performs an offline diff between two manifest files without requiring cluster access.
Examples
- image: nginx:1.24
+ image: nginx:1.26- replicas: 2
+ replicas: 5+ resources:
+ limits:
+ cpu: 500mFrequently Asked Questions
kubectl diff compares a local manifest against the live cluster state and requires cluster access. This tool compares two local manifest files offline. Use this tool during development to review changes; use kubectl diff when you want to see what will change in a live cluster.
Yes. Paste two versions of your values.yaml to compare Helm configuration changes. For diffing rendered Helm output, use helm template to render each version first, then compare the rendered YAML.
YAML anchors and aliases are resolved before diffing. The diff shows the effective values — what the Kubernetes API server would actually receive — rather than the symbolic anchor references.
💡 Tips
- Before applying changes to production, always do an offline diff here <em>and</em> a live <code>kubectl diff</code> to ensure nothing unexpected is different.
- Diff your manifests between Git branches as part of your PR review process — it makes Kubernetes config changes as reviewable as code.
- Look for changes to <code>resource limits</code> and <code>requests</code> carefully — they directly affect cluster scheduling and stability.