k8s-diff

Diff Kubernetes manifests against live clusters or previous renders.

3|1|Updated Nov 29, 2025
One-click install
npx skills add https://github.com/indrasvat/claude-code-skills --skill k8s-diff
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: k8s-diff
Source: https://github.com/indrasvat/claude-code-skills/tree/main/skills/k8s-diff
Command: npx skills add https://github.com/indrasvat/claude-code-skills --skill k8s-diff

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Render Kubernetes manifests (Helm, Kustomize, raw YAML) and diff against a live cluster or previous render, flagging risky changes. Use when you need to preview what will change before applying.

Core Features & Use Cases

  • Diff manifests against a live cluster or git renders to surface drift
  • Supports Helm templates, Kustomize manifests, and plain YAML
  • Detects risk patterns like deprecated APIs, resource drift, and potential rollout issues
  • Use Case: Compare a Helm release against the currently deployed state to validate upgrades before apply.

Quick Start

Provide a path to your manifests and run the k8s-diff skill to see a diff against the live cluster or previous render.

Frequently Asked Questions about k8s-diff

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

FAQPage Schema
How do I diff Kubernetes manifests against a live cluster before deploying?

You can diff Kubernetes manifests against a live cluster by rendering Helm, Kustomize, or raw YAML and comparing the output to the current cluster state to surface drift and deployment risks.

Can I compare Helm templates against the currently deployed state to validate upgrades?

Yes, you can compare a Helm release against the currently deployed state to validate upgrades before applying changes to the Kubernetes cluster.

Does k8s-diff work with Kustomize and plain YAML workflows?

Yes, k8s-diff works with Kustomize manifests, Helm templates, and plain YAML workflows to render manifests and compare them against live clusters or previous git renders.

Do I need kubectl installed to run Kubernetes manifest diffs?

Yes, kubectl is a required prerequisite to run Kubernetes manifest diffs, while helm and kustomize are optional tools needed only if your specific workflow uses those rendering engines.

What risky changes can a Kubernetes manifest diff detect before applying?

A Kubernetes manifest diff can detect risk patterns like deprecated APIs, resource drift against the live cluster, and potential rollout issues before you apply changes.

Can I use Kubernetes manifest diffing in CI contexts to compare git history?

Yes, you can use Kubernetes manifest diffing in CI contexts to compare current renders against previous git history or live clusters to prevent risky deployments.