GitOps with ArgoCD in Kubernetes - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is GitOps in simple terms?

GitOps is a way to manage and deploy applications using Git as the single source of truth. Changes to your app are made by updating Git, and automation tools apply those changes to your system.

beginner

What role does ArgoCD play in GitOps?

ArgoCD is a tool that watches your Git repository and automatically applies the changes to your Kubernetes cluster, keeping your live system in sync with what is defined in Git.

intermediate

How does ArgoCD detect changes in your Git repository?

ArgoCD regularly polls the Git repository or listens for webhooks to detect changes, then compares the live state with the desired state defined in Git and syncs them if needed.

intermediate

What is an Application in ArgoCD?

An Application in ArgoCD is a resource that defines which Git repository and path to use, and which Kubernetes cluster and namespace to deploy to. It represents one deployable unit.

beginner

Why is GitOps with ArgoCD considered safer than manual deployments?

Because all changes go through Git, you have a clear history and audit trail. ArgoCD automatically ensures the cluster matches Git, reducing human errors and making rollbacks easy.

What does ArgoCD use as the source of truth for deployments?

A Git repository

B Local files on the cluster

C Manual commands

D Docker Hub

ArgoCD uses the Git repository as the single source of truth to manage and deploy applications.

Which Kubernetes resource does ArgoCD primarily manage?

A Applications

B ConfigMaps

C Services

D Pods

ArgoCD manages Applications, which define the Git repo, path, and target cluster for deployment.

How does ArgoCD keep the cluster state in sync with Git?

A By manual user commands only

B By running cron jobs on the cluster

C By polling Git and applying changes automatically

D By using Kubernetes Operators

ArgoCD polls the Git repository and automatically applies changes to keep the cluster in sync.

What happens if the live cluster state differs from Git in ArgoCD?

A ArgoCD deletes the application

B ArgoCD alerts but does not fix

C ArgoCD ignores the difference

D ArgoCD syncs the cluster to match Git

ArgoCD syncs the live cluster state to match the desired state defined in Git.

Which of these is NOT a benefit of GitOps with ArgoCD?

A Clear audit trail of changes

B Manual editing of live cluster without Git

C Automatic rollback to previous versions

D Reduced human error in deployments

Manual editing of the live cluster without Git is not a benefit; GitOps encourages all changes through Git.

Explain how ArgoCD uses Git to manage Kubernetes deployments.

Think about how changes in Git lead to updates in the cluster.

Describe the safety advantages of using GitOps with ArgoCD compared to manual deployment.

Consider what happens when you want to track or undo changes.