get_changes
Investigates regressions by retrieving recent meaningful changes, ranked by spec and config updates with field-level diffs for Deployments and ConfigMaps.
Instructions
Use when the symptom is 'this worked earlier' or 'something broke after a deploy/config change.' Returns recent meaningful changes ranked with spec/config changes first, including field-level diffs for Deployment env/probes and structured ConfigMap data when available. This is often faster than reading ReplicaSet histories or individual audit/log streams, especially when issues are empty or dominated by baseline failures. Pair with since to bound the window; filter by namespace, kind, or name when you know the scope. Omit namespace when the relevant change may be outside the app namespace.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| namespace | No | filter to a specific namespace | |
| kind | No | filter to a resource kind (e.g. Deployment, Pod) | |
| name | No | filter to a specific resource name | |
| since | No | duration to look back, e.g. 1h, 30m, 24h (default 1h) | |
| limit | No | max changes to return (default 20, max 50) |