Jeffrey
d5e073131d
The earlier rule covered creationTimestamp, volumeMode and status but missed apiVersion and kind, which the API server also injects into volumeClaimTemplates. Those two alone kept both StatefulSets permanently OutOfSync: a sync would apply successfully and report Synced, then the very next comparison flagged them again.
42 lines
1.5 KiB
YAML
42 lines
1.5 KiB
YAML
apiVersion: argoproj.io/v1alpha1
|
|
kind: Application
|
|
metadata:
|
|
name: infisical
|
|
namespace: argocd
|
|
spec:
|
|
project: default
|
|
source:
|
|
repoURL: https://gitea.jsme.be/Jeffrey/Kubernetes-Manifests.git
|
|
path: applications/infisical
|
|
targetRevision: HEAD
|
|
directory:
|
|
recurse: true
|
|
# secret.yaml holds Infisical's own bootstrap secrets — applied out-of-band,
|
|
# committed here only as an emptied template. Never let ArgoCD apply it.
|
|
exclude: secret.yaml
|
|
destination:
|
|
server: https://kubernetes.default.svc
|
|
namespace: infisical
|
|
# A StatefulSet's volumeClaimTemplates are immutable, and the API server
|
|
# injects fields into them that are not in the manifest: apiVersion, kind,
|
|
# metadata.creationTimestamp, spec.volumeMode and a status block. ArgoCD
|
|
# diffs those and reports OutOfSync forever, since no sync can resolve them.
|
|
# infisical-postgres and infisical-valkey are the only StatefulSets here
|
|
# using volumeClaimTemplates, which is why this app alone was affected.
|
|
ignoreDifferences:
|
|
- group: apps
|
|
kind: StatefulSet
|
|
jqPathExpressions:
|
|
- '.spec.volumeClaimTemplates[]?.apiVersion'
|
|
- '.spec.volumeClaimTemplates[]?.kind'
|
|
- '.spec.volumeClaimTemplates[]?.metadata.creationTimestamp'
|
|
- '.spec.volumeClaimTemplates[]?.spec.volumeMode'
|
|
- '.spec.volumeClaimTemplates[]?.status'
|
|
syncPolicy:
|
|
automated:
|
|
prune: true
|
|
selfHeal: true
|
|
syncOptions:
|
|
- ApplyOutOfSyncOnly=true
|
|
- ServerSideApply=true
|