Notifying the end user
To synchronize applications, Argo CD can work in two different ways. First, it can work manually so that a new commit to the GitOps repo will not have any direct effect unless you trigger the synchronization manually via the CLI, by using the UI, or by using an API call. The second mode, which I think is the most used one, is that after a push to the repo, Argo CD will start to automatically reconcile the cluster state so that it matches the one we declared.
The developers that performed the state changes are interested in the outcome of the reconciliation – they want to know if their microservices are up and running correctly or if they have some problems with the new configuration or the new container image.
Earlier, we learned how to monitor the synchronization process using Prometheus and the metrics Argo CD exposes for application health and synchronization status. However, there is another way we can notify development teams that their microservices...
