observe-flux
OfficialExplain Flux ownership and sources fast.
Software Engineering#helmrelease#kustomization#flux ownership#kubernetes diagnosis#managedFields attribution#source artifacts#gitops drift
Authorconfighub
Version1.0.0
Installs0
System Documentation
What problem does it solve?
It helps you determine whether a Kubernetes resource is managed by Flux and precisely explain where its values came from, why it’s unhealthy or drifting, and which Flux controller and source artifact are responsible.
Core Features & Use Cases
- Flux ownership detection: Identifies Flux-managed resources using controller-specific label families for Kustomizations and HelmReleases.
- Managed-field attribution: Explains which controller wrote observed fields by matching Flux’s exact
metadata.managedFields.managerstrings (kustomize-controller, helm-controller, source-controller). - Trace back to Flux source artifacts: Walks the chain from a workload to its owning Kustomization/HelmRelease, then to the underlying source (GitRepository, OCIRepository, HelmRepository, Bucket, HelmChart) via
spec.sourceRefand source revision evidence.
Quick Start
Ask the skill to explain why a deployment is unhealthy and whether Flux is the real owner, including which Kustomization/HelmRelease and which source artifact produced it.
Dependency Matrix
Required Modules
None requiredComponents
references
💻 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-flux Download link: https://github.com/confighub/cub-scout/archive/main.zip#observe-flux Please download this .zip file, extract it, and install it in the .claude/skills/ directory.
Agent Skills Search Helper
Install a tiny helper to your Agent, search and equip skill from 471,000+ vetted skills library on demand.