About the Diff & Patch Viewer
Comparing two versions of a config, manifest, or code file is the fastest way to answer "what changed?" during an incident. This tool diffs two texts side by side in your browser and exports a unified patch — the same format git diff produces and patch(1) consumes.
Because it runs locally, you can safely diff things you would not paste into an online service: production environment files, Kubernetes manifests pulled from a live cluster versus what's in git, or two versions of a customer config.
Frequently asked questions
What is unified diff format?
The standard text diff representation: @@ hunk headers give line positions, lines prefixed with - were removed, + were added, and unprefixed lines are context. It is what git, GitHub PRs, and patch(1) all speak, so a diff exported here can be applied elsewhere with git apply or patch -p0.
How do I diff what's running in Kubernetes against what's in git?
kubectl get deploy myapp -o yaml gives the live object (strip the status section and runtime metadata), and your repo has the declared manifest. Pasting both here shows exactly what drifted — or use kubectl diff -f manifest.yaml against the cluster directly for the server-side equivalent.
Why does my diff show every line as changed?
Usually invisible differences: CRLF vs LF line endings, tabs vs spaces, or trailing whitespace. Normalize line endings first (dos2unix or your editor) and re-compare. YAML files re-serialized by a tool also commonly reorder keys, which changes every line while being semantically identical.
Need this managed for you, not just automated?
We're also a hands-on DevOps consultancy — Kubernetes, CI/CD, and cloud infrastructure.