Hands-On Microservices with Kubernetes

Using sync policies

By default, Argo CD detects when an application's manifests are out of sync, but doesn't sync automatically. This is a good default. In some cases, more tests need to run in dedicated environments before pushing changes to production. In other cases, a human must be in the loop. However, in many other cases, it's OK to automatically deploy changes to the cluster immediately and without human intervention. The fact that Argo CD follows GitOps also makes it very easy to sync back to any previous version (including the last one).

For Delinkcious, I chose auto sync because it is a demo project and the consequences of deploying a bad version are negligible. This can be done in the UI or from the CLI:

argocd app set <APPNAME> ...