Describe the bug
A git change in one of micorservices triggers restart of all the microservices in the cluster. An argocd app corresponds to each microservice. I am using application-set-controller for these microservices which inturn is installed through app-of-apps pattern. The common part of microservices is a set of common templates and common values.yaml file.
Each microservice has its own values.yaml files also in a microservice specific folder.
If i make a change in one of the apps lets say i change any value in app1/values.yaml, argocd should start only app-1 to make it effective but not app-2.
This was happening due to a timestamp being passed as env variable to the deployments and since it is a dynamic value, it was causing the restart on sync randomly.
Checklist:
argocd version
.Describe the bug A git change in one of micorservices triggers restart of all the microservices in the cluster. An argocd app corresponds to each microservice. I am using application-set-controller for these microservices which inturn is installed through app-of-apps pattern. The common part of microservices is a set of common templates and common values.yaml file. Each microservice has its own values.yaml files also in a microservice specific folder.
To Reproduce App-set-controller definition
Structure of mentioned above looks like this.
Expected behavior
If i make a change in one of the apps lets say i change any value in app1/values.yaml, argocd should start only app-1 to make it effective but not app-2.
Version