k8s-image-audit

Audit Kubernetes deployments for stale images, pull policies, and volume health.

18|2|Updated Dec 12, 2025
One-click install
npx skills add https://github.com/markus41/claude --skill k8s-image-audit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: k8s-image-audit
Source: https://github.com/markus41/claude/tree/main/.claude/skills/k8s-image-audit
Command: npx skills add https://github.com/markus41/claude --skill k8s-image-audit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps identify and resolve issues related to stale container images, incorrect pull policies, and potential caching problems in Kubernetes deployments, ensuring your applications run with the intended and up-to-date images.

Core Features & Use Cases

  • Image Freshness Audit: Checks running pods for outdated container images.
  • Caching Risk Detection: Identifies pods using :latest tags or missing explicit imagePullPolicy, which can lead to unexpected behavior.
  • Helm Release Verification: Compares deployed Helm chart versions and application versions with actual running images.
  • Volume Health Check: Assesses the status of Persistent Volumes (PV) and Persistent Volume Claims (PVC) to detect issues like orphaned PVCs.
  • Build vs. Deploy Cross-Reference: Compares build timestamps with deployment timestamps to flag stale deployments.

Quick Start

Run the k8s-image-audit skill to check the 'production' namespace for stale images and incorrect pull policies.

Frequently Asked Questions about k8s-image-audit

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

FAQPage Schema
How do I check Kubernetes deployments for stale container images?

To check Kubernetes deployments for stale container images, you can run an audit that scans running pods and compares build timestamps with deployment timestamps to flag outdated versions.

Why does Kubernetes use cached images instead of the latest version?

Kubernetes uses cached images when pods use the :latest tag or lack an explicit imagePullPolicy. Auditing pull policies helps detect these caching risks and prevent unexpected deployment behavior.

How do I verify Helm release versions match the running container images?

To verify Helm release versions match running container images, you can perform a Helm release verification that compares deployed chart and application versions against the actual images running in the pods.

Can I detect orphaned Persistent Volume Claims in a specific namespace?

Yes, you can detect orphaned Persistent Volume Claims by running a volume health check that assesses the status of Persistent Volumes (PV) and Persistent Volume Claims (PVC) within your specified namespaces.

Do I need kubectl and jq installed to audit k8s image pull policies?

Yes, you need kubectl and jq installed to audit k8s image pull policies, as they are required for cluster interaction and parsing the JSON data returned from the Kubernetes API.

What is the best way to find pods missing an explicit imagePullPolicy?

The best way to find pods missing an explicit imagePullPolicy is to run a caching risk detection audit that scans the cluster and identifies deployments vulnerable to unexpected image updates.