scout-compare

Compare intended Kubernetes state against live cluster state for drift.

14|Updated Jan 17, 2026
One-click install
npx skills add https://github.com/confighub/cub-scout --skill scout-compare
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: scout-compare
Source: https://github.com/confighub/cub-scout/tree/main/skills/scout-compare
Command: npx skills add https://github.com/confighub/cub-scout --skill scout-compare

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill helps you determine whether a Kubernetes release or configuration landed as intended by comparing intended state (Git/ConfigHub) against actual live cluster state.

Core Features & Use Cases

  • Three-way intent vs live comparison: Confirms agreement across DRY (ConfigHub intent), WET (deploy manifests/bindings), and LIVE (cluster reality), returning structured verdicts.
  • Drift detection from a manifest: Compares a desired YAML file to the live cluster to identify configuration drift without requiring ConfigHub connectivity.
  • Strategy-relative source-truth verdicts: Produces an evidence-based PASS/WATCH/BLOCK/ASK status plus an AGREED/MISMATCH/INCOMPLETE/UNKNOWN source_truth axis under an explicitly declared strategy.
  • Safety-first, read-only behavior: Designed to never mutate cluster state; it outputs evidence and next-step guidance while refusing fixes.

Quick Start

Ask an AI to run: "Compare Deployment/api in namespace prod for drift and provide a structured JSON verdict."

Frequently Asked Questions about scout-compare

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I detect Kubernetes configuration drift between GitOps manifests and live cluster state?

Kubernetes drift detection compares your desired GitOps manifests against the actual live cluster state to identify discrepancies. The skill performs read-only checks and outputs structured verdicts indicating whether the intended configuration is actively running.

What is three-way DRY WET LIVE verification in Kubernetes deployments?

Three-way DRY WET LIVE verification confirms agreement across DRY ConfigHub intent, WET deploy manifests, and LIVE cluster reality. It produces structured verdicts to ensure your Kubernetes release landed exactly as intended across all configuration layers.

Can I use drift detection verdicts for CI gating in Kubernetes pipelines?

Yes, you can use drift detection verdicts for CI gating in Kubernetes pipelines. The skill outputs deterministic structured verdicts suitable for CI gating via the fail-on flag, providing PASS WATCH BLOCK or ASK statuses to block deployments on mismatches.

Does Kubernetes drift detection require ConfigHub connectivity to compare manifests?

Kubernetes drift detection does not require ConfigHub connectivity to compare manifests. You can compare a desired YAML file directly against the live cluster to identify configuration drift, though connecting ConfigHub enables full three-way verification.

Why does the Kubernetes comparison tool refuse to fix configuration drift automatically?

The Kubernetes comparison tool refuses to fix configuration drift automatically because it is designed with safety-first read-only behavior. It never mutates cluster state, instead outputting evidence and next-step guidance to ensure you maintain explicit control over changes.