Tired of writing kubectl get pods or kubectl delete pod? Argo CD is a tool that revolutionizes Kubernetes deployment. It lets you instantly see everything deployed on Kubernetes and whether it’s synchronized with your code repository, following the GitOps philosophy.

How does Argo CD work?

Argo CD connects to a Git repository and deploys the resources defined for the different configured clusters.

git <-- Argo --> sync cluster A / cluster B / cluster C

This keeps your Kubernetes environment aligned with the desired state stored in Git, avoiding manual changes and potential human errors. Using Argo CD is, in many ways, a guarantee of quality and safety, since it eliminates several failure points. And if that’s not convincing enough, here are some of the main benefits of Argo CD.

Benefits of Argo CD

These are only some of the benefits. To fully understand Argo CD, we need to look into its basic concepts.

Basic concepts

Some of the basic concepts you’ll find in the Argo CD admin console include:

As a picture is worth a thousand words, here’s a screenshot showing the key parameters:

dashboard showing healthy, synced, sync ok

Graphical Interface

One of the greatest strengths of Argo CD is its UI: intuitive, clean, and filled with useful information for operators and teams.

Argo CD interface demo

The UI lets you sync applications—goodbye kubectl apply! And if no one is watching, you can even live-edit a file (I won’t judge). The good thing is that Argo CD won’t let it slip—it will remind you that the application is out of sync with Git.

Autosync, prune and autohealing

Let’s say you want to prevent someone from modifying files directly in production. Can Argo CD help? Absolutely! Argo CD offers several synchronization modes:

Sync Windows

As we've seen, Argo CD is an extremely complete tool, right? But there’s more! Argo CD allows multiple configuration types based on your needs. Here are a few examples:

sync window semaphore

Conclusion

Argo CD helps you automate, audit, and simplify the lifecycle of your Kubernetes deployments. Less kubectl, more control, more security. Ready to try it out? Let me know in the comments! 😉

Tell us what you think.

Comments are moderated and will only be visible if they add to the discussion in a constructive way. If you disagree with a point, please, be polite.

Subscribe