audit-fleet-conformance

You can audit Kubernetes fleet drift by running a three-way comparison of DRY, WET, and LIVE states per resource to produce an agreement rollup. This identifies which resources diverge from their declared source-of-truth across your fleet.

GitOps conformance drift is detected by evaluating live Kubernetes resources against ConfigHub-governed intent using strategy-typed source-truth verdicts. This generates PASS, WATCH, or BLOCK evidence quality outcomes suitable for compliance audits.

Fleet outlier detection works by flagging clusters whose data for a specific View scope diverges from fleet expectations. It compares live state against source-of-truth across multiple namespaces to surface non-compliant clusters.

Yes, you can optionally save receipt evidence during a fleet conformance audit. This persists three-way comparison results and strategy-typed verdicts to provide an immutable audit trail for compliance dashboards.

Yes, connected mode is required for View resolution, source-truth evaluation, and fleet outlier reporting. The audit must compose three-way comparisons with strategy checks, which depends on connected ConfigHub integration.

Yes, fleet conformance audits support release gating by evaluating whether live Kubernetes resources agree with declared governance strategies. This ensures resources are reconciled and compliant before proceeding with deployments.