Example: Helm / Argo release inventory¶

Argo CD basics

This walkthrough inventories Argo CD Application CRs. You need Argo CD installed and at least one synced Application in a namespace your target can watch. For Argo CD concepts and CLI usage, see the upstream documentation.

This walkthrough inventories chart version, app version, and sync metadata from Argo CD Application objects. It follows the same four-CRD pipeline as Deployment inventory.

Primary demo GVK (ADR-0201): argoproj.io/v1alpha1 / Application. Contract test: internal/collect/argo_application_contract_test.go. Design rationale: ADR-0303.

Overview¶

flowchart LR
  Profile[KollectProfile<br/>argo-application-summary]
  Target[KollectTarget<br/>select Applications]
  Inv[KollectInventory<br/>aggregate + export]
  Sink[KollectDatabaseSink<br/>Postgres]
  Argo[(Argo CD Application)]
  Profile --> Target
  Target --> Argo
  Target --> Inv
  Inv --> Sink

Step 1 — KollectProfile¶

Summary tier only

Targets argoproj.io/v1alpha1 / Application. Extracts chart and sync metadata — not spec.source.helm.values. Full values inventory requires a future helm: decode path (ADR-0303).

Sample: config/samples/kollect_v1alpha1_kollectprofile_argo-application-summary.yaml

apiVersion: kollect.dev/v1alpha1
kind: KollectProfile
metadata:
  name: argo-application-summary
  namespace: default
spec:
  targetGVK:
    group: argoproj.io
    version: v1alpha1
    kind: Application
  attributes:
    - name: chart
      path: '$.spec.source.chart'
      type: string
      optional: true
    - name: chartVersion
      path: '$.status.sync.revision'
      type: string
      optional: true
    - name: syncStatus
      path: '$.status.sync.status'
      type: string
      optional: true
    # ... the sample file also extracts targetRevision, appVersion, and revision

Step 2 — KollectDatabaseSink¶

Namespaced (ADR-0201). Default inventory uses Postgres: config/samples/kollect_v1alpha1_kollectdatabasesink.yaml. See Postgres state store.

Step 3 — KollectTarget¶

config/samples/kollect_v1alpha1_kollecttarget_argo-applications.yaml

spec:
  profileRef: argo-application-summary
  namespaceSelector:
    matchLabels:
      argocd.argoproj.io/instance: team-a

profileRef resolves in the same namespace as the target.

Step 4 — KollectInventory¶

config/samples/kollect_v1alpha1_kollectinventory.yaml — databaseSinkRefs: [postgres-inventory-demo].

Apply¶

kubectl apply -k config/samples/

Flux HelmRelease (secondary)¶

File	Purpose
`kollect_v1alpha1_kollectprofile_helm-release-summary.yaml`	Flux summary profile
`kollect_v1alpha1_kollecttarget_helm-releases.yaml`	Flux target

Attribute	Path
`chartVersion`	`$.status.lastAttemptedRevision`
`appVersion`	`$.status.history[0].appVersion`
`valuesChecksum`	`$.status.lastAttemptedConfigDigest`

Troubleshooting¶

Optional attributes

chartVersion and syncStatus are marked optional: true — empty export rows are normal when an Application has not synced yet. Check kubectl get application -A before assuming a profile bug.

Symptom	Likely cause
Profile not found	`profileRef` must be in same namespace as target
Empty chartVersion	Application not synced (`optional: true`)
No export	Postgres DSN missing or `ConnectionVerified=False`

ADR-0303 · Deployment inventory