observe-helm

Official

Disambiguate Helm ownership across controllers

Authorconfighub
Version1.0.0
Installs0

System Documentation

What problem does it solve?

This skill resolves confusion about what “Helm-managed” really means for a Kubernetes resource by separating direct Helm installs from Helm applied via Flux or rendered by Argo CD, so you can trace each field back to its true source.

Core Features & Use Cases

  • Helm-via-disambiguation matrix: Uses metadata.managedFields manager-string co-signals plus Helm label families to classify ownership as direct Helm, Flux helm-controller (HelmRelease), or Argo CD as a Helm renderer.
  • Helm ownership detection signals: Detects Helm releases using app.kubernetes.io/managed-by: Helm with app.kubernetes.io/instance, and falls back to helm.sh/chart when needed (including legacy charts).
  • Practical investigations: Helps answer which chart produced a Deployment/API object, why app.kubernetes.io/managed-by: Helm appears, and what the next best diagnostic step should be.

Quick Start

Use observe-helm to determine whether a specific Deployment in your cluster is owned by direct Helm, Flux helm-controller, or Argo CD rendering a Helm chart.

Dependency Matrix

Required Modules

None required

Components

Standard package

💻 Claude Code Installation

Recommended: Let Claude install automatically. Simply copy and paste the text below to Claude Code.

Please help me install this Skill:
Name: observe-helm
Download link: https://github.com/confighub/cub-scout/archive/main.zip#observe-helm

Please download this .zip file, extract it, and install it in the .claude/skills/ directory.
View Source Repository

Agent Skills Search Helper

Install a tiny helper to your Agent, search and equip skill from 471,000+ vetted skills library on demand.