Kubernetes manifest diff
Compare two sets of Kubernetes manifests by resource, see which fields changed with their lines on both sides, and find the changes that start a new rollout.
Up to 1,000,000 characters on each side, 100 documents and 5,000 objects per side. Everything runs on your device in a background worker. Downloads: unified diff, JSON report and CSV of changed fields. Paste the current manifests. Separate documents with ---. Up to 1,000,000 characters. Review the settings before running.
Your result
How to use Kubernetes manifest diff
- Paste the current manifests in the main box.
- Paste the changed manifests in the After box.
- Set the namespace used for objects without one.
- Run the comparison and download the diff, JSON report or CSV.
Useful next steps
How resources are matched
Happytails.ai matches objects by API group, kind, namespace and name, so reordering documents or changing the API version does not count as a change. Lists such as containers, env, ports and volumes are matched by their merge key, for example the container name, like kubectl does with strategic merge patches.
What the output shows
The unified diff shows each added, removed or changed resource as clean YAML. The JSON report lists every changed field with its line in the before and after text. A change inside a pod template is marked as a rollout, because Deployments, StatefulSets, DaemonSets, ReplicaSets and Jobs start new pods for it.
Limits
Server-managed fields such as status, managedFields, resourceVersion, uid and the last-applied annotation are ignored. Defaults that the API server would add are not filled in, so a field you omit and a field set to its default show as different.