[argo-cd] Application in any namespace | Synced with NO resources deployed

[ironoa]

Describe the bug

Maybe someone can help me debug an issue I'm facing:

I have an ArgoCD instance deployed with helm, chart version 5.16.2

I'm trying to enable the application-in-any-namespace feature... basically I added the application.namespaces: '*' config as a configs.params value.

When I deploy an Application in a namespace which is not the one where argocd is installed, the application now gets recognized (thanks to the above mentioned config), but it becomes immediately synced without deploying anything else... I'm also not getting any errors anywhere apparently...

FYI

• I defined a dedicated AppProject with the spec.sourceNamespaces: '*' config.
• The very same Application deployed in the argocd (my std) namespace produces the expected result instead

Any hint ? thanks

Related helm chart

argo-cd

Helm chart version

5.16.2

To Reproduce

• deploy Argocd chart, configure the value configs.params with application.namespaces: '*'
• deploy an AppProject with the spec.sourceNamespaces: '*' config
• deploy an Application (which uses the Project defined in the previous step) in a namespace which is not the Argo one
• the Application will get recognized, but no further resources will get deployed

Expected behavior

When I deploy an Application in a namespace which is not the one where argocd is installed, the application now gets recognized (thanks to the above mentioned config), but it becomes immediately synced without deploying anything else (pods, svc, ...)... I'm also not getting any errors anywhere apparently...

The very same Application deployed in the argocd (my std) namespace produces the expected result instead

Screenshots

Additional context

No response

[ironoa]

still not solved, a bit more interaction about the topic here

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[atamgp]

@ironoa was this eventually solved for you in newest releases?