Detect Argo CD ownership and interpret managed-field attribution for Kubernetes resources.
npx skills add https://github.com/confighub/cub-scout --skill observe-argocd
Please help me install this Agent Skill. Skill: observe-argocd Source: https://github.com/confighub/cub-scout/tree/main/skills/observe-argocd Command: npx skills add https://github.com/confighub/cub-scout --skill observe-argocd
When a Kubernetes resource’s state looks wrong or confusing, it can be hard to determine whether Argo CD owns it and what Argo actually wrote into managed fields.
argocd.argoproj.io/instance and argocd.argoproj.io/tracking-id.metadata.managedFields[].manager is interpreted for Argo vs client-side apply ambiguity, including CSA migration edge cases.Use observe-argocd to explain whether a specific Deployment is managed by Argo CD and what Argo signaled about its source and managed-field writer.
High-intent search queries and answers about installing and using this skill.
Argo CD ownership detection checks for specific labels like argocd.argoproj.io/instance and tracking-id annotations. Priority-based classification rules confirm whether Argo CD manages the resource and explain its source attribution.
The tracking-id annotation provides Argo-specific ownership context for a Kubernetes resource. Interpreting this annotation helps trace which Argo Application or ApplicationSet generator produced and manages the target workload.
ApplicationSet generator tracing uses Argo detection signals and tracking-id annotations to identify the parent ApplicationSet. This explains the generator-related context and source attribution for the generated Application.
Managed-field writer interpretation disambiguates kubectl-client-side-apply entries into Argo CSA migration cases versus manual kubectl apply. Priority-based classification rules determine the actual ownership despite the ambiguous manager name.
Diagnosing CSA migration ambiguity requires interpreting metadata.managedFields writer-manager attribution. The analysis disambiguates whether kubectl-client-side-apply indicates Argo client-side apply migration or manual kubectl operations.
Yes, observe-argocd explains Argo-specific ownership and managed-field attribution. It interprets metadata.managedFields manager entries and applies priority rules to clarify what Argo CD owns and wrote into the resource.
NaveedTechLabDeploy Kubernetes applications using Argo CD GitOps workflows and manifests.
RyderFreeman4LogosApply pending migrations to update CSA project configuration and weave.lock state.
cosmixReconcile Git-defined application state with live Kubernetes clusters using Argo CD.
confighubClassify Kubernetes resource ownership as direct Helm, Flux, or Argo CD.