Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Sync issue with argo-cd helm chart 7.4.x #19582

Open
jascsch opened this issue Aug 19, 2024 · 7 comments
Open

Sync issue with argo-cd helm chart 7.4.x #19582

jascsch opened this issue Aug 19, 2024 · 7 comments
Labels

Comments

@jascsch
Copy link

jascsch commented Aug 19, 2024

Checklist:

  • [ x ] I've searched in the docs and FAQ for my answer: https://bit.ly/argocd-faq.
  • [ x ] I've included steps to reproduce the bug.
  • [ x ] I've pasted the output of argocd version.

Describe the bug

There is a sync issue with argocd version v2.12.1 so that apps are stuck in "OutOfSync" status.

To Reproduce

use the following manifest and try to sync the dapr app.

project: default
destination:
  server: 'https://kubernetes.default.svc'
  namespace: dapr
syncPolicy:
  syncOptions:
    - CreateNamespace=true
    - RespectIgnoreDifferences=true
ignoreDifferences:
  - kind: Secret
    name: dapr-trust-bundle
    namespace: dapr
    jsonPointers:
      - /data
sources:
  - repoURL: 'https://dapr.github.io/helm-charts/'
    targetRevision: 1.11.1
    helm:
      valueFiles:
        - $values/tools/dapr/values.yaml
      releaseName: dapr
      skipCrds: true
    chart: dapr
  - repoURL: 'https://git.xxx.com/org/gitops-cluster-dev.git'
    targetRevision: HEAD
    ref: values

Expected behavior

The sync status should be "Synced" instead of "OutOfSync"
The sync works perfectly fine with helm chart version 7.3.x

Screenshots

image

Version

argocd v2.12.1
helm chart argo-cd-7.4.4

Logs

no relevant application logs available.
@moksongmin
Copy link

I have a similar issue:

I use Crossplane to provision an AWS RDS Instance. I've added an 'identifier' parameter to two of my instances, and it can't be synced in ArgoCD (v7.4.1).

image

image

*Note: I haven't tested with previous 7.3.X version.

@grv180290
Copy link

Try using Ignore difference to get rid of this OutofSync status
https://argo-cd.readthedocs.io/en/stable/user-guide/diffing/#application-level-configuration

@jascsch
Copy link
Author

jascsch commented Sep 9, 2024

I am already using Ignore difference like this:

ignoreDifferences:
  - kind: Secret
    name: dapr-trust-bundle
    namespace: dapr
    jsonPointers:
      - /data

What else do we have to do to get rid of this issue?

@moksongmin
Copy link

ignoreDifferences worked for me, as well.

@jascsch
Copy link
Author

jascsch commented Sep 13, 2024

Hi @moksongmin can you please paste an example of your manifest with ignoreDifferences which worked in your case?

@moksongmin
Copy link

Hi @jascsch, sure, here it is:
image

@mkilchhofer
Copy link
Member

As already analyzed in argo-helm (argoproj/argo-helm#2883), I think this is completely normal since your (EOL) Dapr helm chart is using the non-idempotent sprig function genSignedCert to generate the webhook TLS secrets:

It seems that Dapr 1.12 does no longer use this (the webhook deployment iself now takes care of this - although I assume that you also need an Argo CD "ignoreDifferences" for this):

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

5 participants