Earlier this year, when Codefresh announced the first course in our GitOps for Argo certification program – GitOps Fundamentals – we had high hopes that the course would satisfy the community’s pent-up demand for practical GitOps knowledge. To meet this demand, we designed a course that features lab environments to dramatically improve the learning experience. Each student gets a lab environment pre-configured with everything they need to learn GitOps using Argo CD.

We have already covered several aspects of Argo CD in this blog such as best practices, cluster topologies and even application ordering, but it is always good to get back to basics and talk about installation and more importantly about maintenance. Chances are that one of your first Argo CD installations happened with kubectl as explained in the getting started guide.

At the start of this year, Codefresh announced the first ever GitOps certification for Argo CD. The certification consists of 3 different levels covering GitOps end-to-end from beginning to end. With the launch of Level 1 (Fundamentals), we have seen an unprecedented interest from people that want to learn about GitOps resulting in over 10,000 students and 3,000 certified engineers!

If you are using Argo CD, you may be already familiar with how the Application CRD (Custom Resource Definition) object helps you logically group together your Kubernetes Manifests. The Application object is the atomic unit of work in Argo CD, and you should think of all your Kubernetes objects that are in an Application as a single entity. Applications are also autonomous. Meaning that, by design, one Application doesn’t know about the status or health of another Application.

Many organizations that have already implemented a DevOps culture are looking to further accelerate their development process by adopting GitOps practices in their environments. There is a lot to take into consideration when planning out your GitOps strategy, and you can read more about it at this Codefresh learning center about adopting GitOps.