-
Notifications
You must be signed in to change notification settings - Fork 83
Argo CD: drift: persistent volume claim #248
Copy link
Copy link
Open
Labels
bugSomething isn't workingSomething isn't workingneeds triageWaiting for discussion / prioritization by teamWaiting for discussion / prioritization by team
Description
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: databaseThe 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
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
bugSomething isn't workingSomething isn't workingneeds triageWaiting for discussion / prioritization by teamWaiting for discussion / prioritization by team