> ## Documentation Index
> Fetch the complete documentation index at: https://autopilot.docs.xano.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Resource Audit

> Compare each workload's deploy template, Autopilot recommendation, and live pod resources — spot drift, and remediate it in one click or in bulk.

The **Resource Audit** page puts three numbers side by side for every workload — what the
**deploy template** requests, what Autopilot **recommends**, and what the **live pod** is
actually running — and flags where they've drifted apart. It's the vertical (sizing)
counterpart to [HPA Audit](/platform/hpa-audit): a place to find workloads whose resources are
stale, mis-set, or diverged, and put them right.

## What drift looks like

Over time a workload's live resources can diverge from its template for legitimate reasons (an
in-place resize, an OOM bump, an operator floor) or accidental ones (a stale annotation, a
half-applied change). The audit makes each visible:

* **template vs recommendation** — the workload is over- or under-provisioned relative to what usage says it needs.
* **template vs pod** — the running pod no longer matches what the Deployment declares.
* **QoS drift** — the template is Guaranteed but the live pod is Burstable (or vice-versa), which affects eviction priority.

Filter by namespace, kind, drift type, whether a recommendation exists, or whether the workload
carries Autopilot annotations. QoS-specific filters (`truly-guaranteed`, `drift`) isolate the
workloads where QoS class matters.

## Remediation

Each row offers targeted, idempotent actions — and any of them can be applied in **bulk** to up
to 500 workloads at once (concurrency-limited, with per-item error reporting):

| Action                    | What it does                                                                                                                                                                                               |
| ------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Reset to deploy**       | Strip Autopilot's resize annotations, delete the Recommendation CRD **and** the workload's LimitExceptions, then trigger a rollout restart — returning the workload to exactly what its template declares. |
| **Delete recommendation** | Remove only the Recommendation CRD (idempotent).                                                                                                                                                           |
| **Strip annotations**     | Remove only the Autopilot resize annotations (idempotent).                                                                                                                                                 |

<Note>
  Every action is blocked on the controller's own namespace (`ops-ai`) — Autopilot never resets
  or restarts itself. "Reset to deploy" also clears LimitExceptions so a stale exception's reject
  can't later revert the workload back toward its pre-reset values.
</Note>

## When to use it

* **After a migration** or a period of manual tuning, to find workloads that drifted and reconcile them to a known-good baseline.
* **To undo Autopilot on a specific workload** — "reset to deploy" is the clean off-switch for one workload's sizing.
* **To spot QoS drift** before it causes a surprise eviction ordering.

The page is in the **Optimization** navigation area. For setting hard bounds on what Autopilot
may recommend (rather than resetting), see [Resource Overrides](/platform/resource-overrides).