crd-impact

Map Kubernetes CRD change blast radius across controllers, webhooks, RBAC, and manifests.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Read-only analysis of CRD change blast radius across controllers, webhooks, RBAC, manifests, and clients.

Core Features & Use Cases

  • Identify all controllers, webhooks, RBAC rules, and manifests referencing the CRD.
  • Baseline diff against git history to surface added, removed, and changed fields.
  • Produce an impact map detailing which files and components are affected, with recommended actions.
  • Use cases include evaluating the impact of CRD schema changes before upgrades or deployments.

Quick Start

Provide the CRD YAML file path or group/version/kind to run an impact analysis across controllers, webhooks, RBAC, and manifests.

Frequently Asked Questions about crd-impact

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

FAQPage Schema
How do I analyze the blast radius of a Kubernetes CRD schema change?

To analyze the blast radius of a Kubernetes CRD schema change, you provide a CRD file path or group/version/kind. The tool statically analyzes the codebase to list all affected controllers, webhooks, RBAC bindings, and manifests.

How do I find which controllers and webhooks reference a specific CRD?

Finding controllers and webhooks that reference a specific CRD involves static analysis of the Kubernetes codebase. The tool scans and maps all file dependencies, producing an impact map that classifies affected components.

Can I diff CRD schema changes against git history to find affected manifests?

Yes, you can diff CRD schema changes against git history. The analysis baselines against previous commits to surface added, removed, and changed fields, categorizing the required updates for affected manifests.

How do I check RBAC binding impact before upgrading a CRD?

Checking RBAC binding impact before upgrading a CRD involves scanning the codebase for referencing rules. The analysis identifies these bindings and classifies the necessary updates from MUST UPDATE to INFORMATIONAL.

What is the best way to map CRD changes to affected Kubernetes clients and manifests?

The best way to map CRD changes to affected Kubernetes clients and manifests is a read-only impact analysis. It evaluates schema modifications before deployment and generates a detailed impact map of affected files.

Do I need to provide a full CRD YAML file path to get an impact map?

No, you do not need to provide a full CRD YAML file path. You can alternatively supply the group/version/kind identifier to run the impact analysis across controllers, webhooks, RBAC, and manifests.