Skip to content

Argo CD: drift: persistent volume claim #248

@volker-raschek

Description

@volker-raschek

Hey,
I've deployed steps-ca with ArgoCD. I receive several notifications, that steps-ca has been successfully synced, even though nothing has been changed.

I investigated some time to analyze the issue and found that the chart does not specify the apiVersion and kind attribute of the mounted persistentVolumeClaim. The following diff highlights the missing attributes, which triggers Argo CD to perform a sync.

  volumeClaimTemplates:
+   - apiVersion: v1
+     kind: PersistentVolumeClaim
+     metadata:
-   - metadata
        labels:
          app.kubernetes.io/instance: step-certificates
          app.kubernetes.io/managed-by: Helm
          app.kubernetes.io/name: step-certificates
        name: database

The current workaround is to ignore the occurrence:

apiVersion: argoproj.io/v1alpha1
kind: Application
metadata:
  name: steps-ca
spec:
  project: default
  ignoreDifferences:
  - group: apps
    kind: StatefulSet
    jqPathExpressions:
    - '.spec.volumeClaimTemplates[0]'

Volker

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't workingneeds triageWaiting for discussion / prioritization by team

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions