See one example
Our live gap test changed replicas and a container environment variable. The current comparison found the replica change but missed the environment-variable change.
That makes this result a warning, not a pass. A clean report covers only the fields named by the receipt.
What each path can tell you
Local files or OCI
Runs on your laptop.
Live comparison: No live comparison runs unless you choose a separate cluster check.
Removal: Not applicable until something deploys the files.
Conflicts: No apply conflict exists until a delivery tool writes to Kubernetes.
A green result means: The local files passed the named local checks. Nothing is claimed about a cluster.
kubectl apply
Needs a Kubernetes cluster; no ConfigHub account is required.
Live comparison: A separate kubectl or cub-scout check can compare selected desired and live fields.
Removal: Ordinary kubectl apply does not delete an object omitted from the next file set.
Conflicts: Server-side apply reports field ownership conflicts; the current resolution workflow remains awkward.
A green result means: The Kubernetes API accepted the apply. Workload readiness and complete convergence need separate checks.
Argo CD or Flux
Needs a registry and cluster; a ConfigHub account is optional.
Live comparison: The controller reports sync or reconciliation for the objects it manages.
Removal: Omitted objects are deleted only when pruning is enabled and tested for that path.
Conflicts: Apply and ownership conflicts appear in controller status and must be resolved deliberately.
A green result means: The controller reconciled its declared objects. Application health and external prerequisites need separate checks.
ConfigHub plus Argo CD or Flux
Needs a ConfigHub account; live comparison also needs a cluster.
Live comparison: ConfigHub keeps the approved desired revisions; current observation receipts compare only their named fields with live state.
Removal: The downstream Argo CD or Flux path removes omitted objects only when pruning is enabled and tested.
Conflicts: ConfigHub shows source and variant changes for review; delivery-time field ownership conflicts still come from Kubernetes or the controller.
A green result means: Approval and publication prove the desired release record. Controller sync, workload health, and live observation remain separate results.
Check the record
Open the live drift receipt. The plain-English summary shows the detected field and the missed field.
Check removal behavior and check field conflicts separately.
Do this next
Read the current gap before you choose a desired-versus-live check for production.