ArgoCD • Flux • Continuous Delivery

🔄

GitOps

// INTERVIEW & ARCHITECTURE HANDBOOK

ArgoCD • Flux • Continuous Delivery

Learn GitOps core architecture, production scenario-based questions, incident response, and real-world engineering solutions.

🔄 GitOps: Interactive Q&A Handbook

🟢 GitOps Advanced Q&A

❓ Q1: What is GitOps, and what are its core operational principles?

Click on the dropdown below to reveal the technical answer.

💡 Reveal Technical Answer

Answer: GitOps is an operational framework that takes DevOps best practices used for application development—such as version control, collaboration, compliance, and CI/CD—and applies them to infrastructure automation.

Key Principles:

Declarative System: The system state is defined declaratively (e.g., using Kubernetes manifests, Helm, or Terraform).
Single Source of Truth: The desired state is stored in Git.
Automatic Pulling: Software agents (like ArgoCD or Flux) automatically pull changes from Git and apply them to the target environment.
Reconciliation Loop: The agent continuously monitors the system and reconciles any drift between the desired state (Git) and the actual state (cluster).

❓ Q2: Why should an organization adopt GitOps? What are the primary benefits?

Click on the dropdown below to reveal the technical answer.

💡 Reveal Technical Answer

Answer:

Security: No need to store access keys in external CI runners; agents pull state changes internally.
Auditability: Git commit logs serve as a chronological audit trail of who changed what, when, and why.
Disaster Recovery: If a cluster is destroyed, all configuration states can be restored to a new cluster instantly by pointing the GitOps agent back to the Git repository.
Self-Healing: Automatically corrects manual "configuration drift" in target environments by reverting changes back to the Git state.

❓ Q3: Can you walk me through the key architectural components of ArgoCD?

Click on the dropdown below to reveal the technical answer.

💡 Reveal Technical Answer

Answer: ArgoCD runs as a set of Kubernetes controllers:

API Server: Exposes the REST/gRPC API for Web UI and CLI authentication.
Repository Server: Clones Git repositories and generates Kubernetes manifests (supporting Helm, Kustomize, Jsonnet).
Application Controller: Monitors the running applications, compares the active state against the repository manifests, and performs sync operations.

❓ Q4: How does FluxCD's architecture differ from ArgoCD, and what are its key controllers?

Click on the dropdown below to reveal the technical answer.

💡 Reveal Technical Answer

Answer: FluxCD uses the GitOps Toolkit (GOTK), which consists of specialized controller microservices:

Source Controller: Syncs Git/Helm repositories.
Kustomize Controller: Applies Kustomize overlays.
Helm Controller: Manages Helm chart releases.
Notification Controller: Handles inbound webhooks and outbound alerts (e.g., Slack notifications).

❓ Q5: What is the difference between a Pull-based GitOps model and a traditional Push-based CI/CD pipeline?

Click on the dropdown below to reveal the technical answer.

💡 Reveal Technical Answer

Answer:

Push Model (Traditional):
- How it works: A CI/CD runner (e.g., Jenkins, GitHub Actions) executes scripts and runs command-line tools to push changes directly to target environments (e.g., executing kubectl apply or terraform apply).
- Cons: Requires sharing admin keys/secrets with the CI runner.
Pull Model (GitOps):
- How it works: An agent runs inside the target cluster (e.g., ArgoCD). It watches the Git repository and pulls configuration changes, applying them locally.
- Pros: Zero external credentials required for deployments; secure network configuration; handles automatic drift correction.

❓ Q6: What are Sync Waves in ArgoCD, and how do they help manage complex multi-tier applications?

Click on the dropdown below to reveal the technical answer.

💡 Reveal Technical Answer

Answer: Sync Waves allow ordering how resources are applied during an ArgoCD sync operation.

Resources are assigned wave integers using metadata annotations (e.g., argocd.argoproj.io/sync-wave: "5").
ArgoCD processes waves from lowest to highest, waiting for resources in wave $N$ to be healthy before executing wave $N+1$. Useful for deploying databases before launching applications.

❓ Q7: How does drift detection work in a GitOps setup? What mechanisms monitor for changes?

Click on the dropdown below to reveal the technical answer.

💡 Reveal Technical Answer

Answer: Drift Detection is the process where the GitOps agent continuously queries the cluster state and compares it against the Git configurations. If an engineer manually edits a deployment replica count in the cluster, the agent flags the application status as OutOfSync and triggers alerts.

❓ Q8: How does Auto Sync work in GitOps, and when would you choose to disable it in production?

Click on the dropdown below to reveal the technical answer.

💡 Reveal Technical Answer

Answer: When Auto Sync is enabled, the GitOps agent automatically overwrites any manual cluster modifications and applies the Git configuration to resolve the drift, returning the cluster to the declared state. When to disable: During large database updates, active debugging incidents, or when running temporary configuration experiments directly on the cluster.

❓ Q9: Imagine a bad deployment goes out via GitOps. How would you execute a rollback in ArgoCD?

Click on the dropdown below to reveal the technical answer.

💡 Reveal Technical Answer

Answer:

Git-Based Rollback (Best Practice): Revert the bad commit in Git (git revert <commit-hash>) and push. The agent detects the change and automatically syncs the cluster.
ArgoCD UI/CLI Rollback: Disable auto-sync temporarily and trigger a manual rollback to a previous release version in the ArgoCD console.

❓ Q10: How do you scale GitOps configurations across multiple clusters in an enterprise environment?

Click on the dropdown below to reveal the technical answer.

💡 Reveal Technical Answer

Answer: Use the App-of-Apps pattern or ArgoCD ApplicationSets. An ApplicationSet uses generators (Git directories, list of clusters, cluster labels) to dynamically create and target multiple application configurations across dev, staging, and production clusters from a single template definition.

ArgoCD • Flux • Continuous Delivery

🔄

GitOps

// INTERVIEW & ARCHITECTURE HANDBOOK

ArgoCD • Flux • Continuous Delivery

Learn GitOps core architecture, production scenario-based questions, incident response, and real-world engineering solutions.

🔄 GitOps: Interactive Q&A Handbook

🟢 GitOps Advanced Q&A

❓ Q1: What is GitOps, and what are its core operational principles?

Click on the dropdown below to reveal the technical answer.

💡 Reveal Technical Answer

Key Principles:

Declarative System: The system state is defined declaratively (e.g., using Kubernetes manifests, Helm, or Terraform).
Single Source of Truth: The desired state is stored in Git.
Automatic Pulling: Software agents (like ArgoCD or Flux) automatically pull changes from Git and apply them to the target environment.
Reconciliation Loop: The agent continuously monitors the system and reconciles any drift between the desired state (Git) and the actual state (cluster).

❓ Q2: Why should an organization adopt GitOps? What are the primary benefits?

Click on the dropdown below to reveal the technical answer.

💡 Reveal Technical Answer

Answer:

Security: No need to store access keys in external CI runners; agents pull state changes internally.
Auditability: Git commit logs serve as a chronological audit trail of who changed what, when, and why.
Disaster Recovery: If a cluster is destroyed, all configuration states can be restored to a new cluster instantly by pointing the GitOps agent back to the Git repository.
Self-Healing: Automatically corrects manual "configuration drift" in target environments by reverting changes back to the Git state.

❓ Q3: Can you walk me through the key architectural components of ArgoCD?

Click on the dropdown below to reveal the technical answer.

💡 Reveal Technical Answer

Answer: ArgoCD runs as a set of Kubernetes controllers:

API Server: Exposes the REST/gRPC API for Web UI and CLI authentication.
Repository Server: Clones Git repositories and generates Kubernetes manifests (supporting Helm, Kustomize, Jsonnet).
Application Controller: Monitors the running applications, compares the active state against the repository manifests, and performs sync operations.

❓ Q4: How does FluxCD's architecture differ from ArgoCD, and what are its key controllers?

Click on the dropdown below to reveal the technical answer.

💡 Reveal Technical Answer

Answer: FluxCD uses the GitOps Toolkit (GOTK), which consists of specialized controller microservices:

Source Controller: Syncs Git/Helm repositories.
Kustomize Controller: Applies Kustomize overlays.
Helm Controller: Manages Helm chart releases.
Notification Controller: Handles inbound webhooks and outbound alerts (e.g., Slack notifications).

❓ Q5: What is the difference between a Pull-based GitOps model and a traditional Push-based CI/CD pipeline?

Click on the dropdown below to reveal the technical answer.

💡 Reveal Technical Answer

Answer:

Push Model (Traditional):
- How it works: A CI/CD runner (e.g., Jenkins, GitHub Actions) executes scripts and runs command-line tools to push changes directly to target environments (e.g., executing kubectl apply or terraform apply).
- Cons: Requires sharing admin keys/secrets with the CI runner.
Pull Model (GitOps):
- How it works: An agent runs inside the target cluster (e.g., ArgoCD). It watches the Git repository and pulls configuration changes, applying them locally.
- Pros: Zero external credentials required for deployments; secure network configuration; handles automatic drift correction.

❓ Q6: What are Sync Waves in ArgoCD, and how do they help manage complex multi-tier applications?

Click on the dropdown below to reveal the technical answer.

💡 Reveal Technical Answer

Answer: Sync Waves allow ordering how resources are applied during an ArgoCD sync operation.

Resources are assigned wave integers using metadata annotations (e.g., argocd.argoproj.io/sync-wave: "5").
ArgoCD processes waves from lowest to highest, waiting for resources in wave $N$ to be healthy before executing wave $N+1$. Useful for deploying databases before launching applications.

❓ Q7: How does drift detection work in a GitOps setup? What mechanisms monitor for changes?

Click on the dropdown below to reveal the technical answer.

💡 Reveal Technical Answer

❓ Q8: How does Auto Sync work in GitOps, and when would you choose to disable it in production?

Click on the dropdown below to reveal the technical answer.

💡 Reveal Technical Answer

❓ Q9: Imagine a bad deployment goes out via GitOps. How would you execute a rollback in ArgoCD?

Click on the dropdown below to reveal the technical answer.

💡 Reveal Technical Answer

Answer:

Git-Based Rollback (Best Practice): Revert the bad commit in Git (git revert <commit-hash>) and push. The agent detects the change and automatically syncs the cluster.
ArgoCD UI/CLI Rollback: Disable auto-sync temporarily and trigger a manual rollback to a previous release version in the ArgoCD console.

❓ Q10: How do you scale GitOps configurations across multiple clusters in an enterprise environment?

Click on the dropdown below to reveal the technical answer.

💡 Reveal Technical Answer

🔄 GitOps: Interactive Q&A Handbook#

🟢 GitOps Advanced Q&A#

❓ Q1: What is GitOps, and what are its core operational principles?#

Key Principles:#

❓ Q2: Why should an organization adopt GitOps? What are the primary benefits?#

❓ Q3: Can you walk me through the key architectural components of ArgoCD?#

❓ Q4: How does FluxCD's architecture differ from ArgoCD, and what are its key controllers?#

❓ Q5: What is the difference between a Pull-based GitOps model and a traditional Push-based CI/CD pipeline?#

❓ Q6: What are Sync Waves in ArgoCD, and how do they help manage complex multi-tier applications?#

❓ Q7: How does drift detection work in a GitOps setup? What mechanisms monitor for changes?#

❓ Q8: How does Auto Sync work in GitOps, and when would you choose to disable it in production?#

❓ Q9: Imagine a bad deployment goes out via GitOps. How would you execute a rollback in ArgoCD?#

❓ Q10: How do you scale GitOps configurations across multiple clusters in an enterprise environment?#

🔄 GitOps: Interactive Q&A Handbook#

🟢 GitOps Advanced Q&A#

❓ Q1: What is GitOps, and what are its core operational principles?#

Key Principles:#

❓ Q2: Why should an organization adopt GitOps? What are the primary benefits?#

❓ Q3: Can you walk me through the key architectural components of ArgoCD?#

❓ Q4: How does FluxCD's architecture differ from ArgoCD, and what are its key controllers?#

❓ Q5: What is the difference between a Pull-based GitOps model and a traditional Push-based CI/CD pipeline?#

❓ Q6: What are Sync Waves in ArgoCD, and how do they help manage complex multi-tier applications?#

❓ Q7: How does drift detection work in a GitOps setup? What mechanisms monitor for changes?#

❓ Q8: How does Auto Sync work in GitOps, and when would you choose to disable it in production?#

❓ Q9: Imagine a bad deployment goes out via GitOps. How would you execute a rollback in ArgoCD?#

❓ Q10: How do you scale GitOps configurations across multiple clusters in an enterprise environment?#

🔄 GitOps: Interactive Q&A Handbook

🟢 GitOps Advanced Q&A

❓ Q1: What is GitOps, and what are its core operational principles?

Key Principles:

❓ Q2: Why should an organization adopt GitOps? What are the primary benefits?

❓ Q3: Can you walk me through the key architectural components of ArgoCD?

❓ Q4: How does FluxCD's architecture differ from ArgoCD, and what are its key controllers?

❓ Q5: What is the difference between a Pull-based GitOps model and a traditional Push-based CI/CD pipeline?

❓ Q6: What are Sync Waves in ArgoCD, and how do they help manage complex multi-tier applications?

❓ Q7: How does drift detection work in a GitOps setup? What mechanisms monitor for changes?

❓ Q8: How does Auto Sync work in GitOps, and when would you choose to disable it in production?

❓ Q9: Imagine a bad deployment goes out via GitOps. How would you execute a rollback in ArgoCD?

❓ Q10: How do you scale GitOps configurations across multiple clusters in an enterprise environment?

🔄 GitOps: Interactive Q&A Handbook

🟢 GitOps Advanced Q&A

❓ Q1: What is GitOps, and what are its core operational principles?

Key Principles:

❓ Q2: Why should an organization adopt GitOps? What are the primary benefits?

❓ Q3: Can you walk me through the key architectural components of ArgoCD?

❓ Q4: How does FluxCD's architecture differ from ArgoCD, and what are its key controllers?

❓ Q5: What is the difference between a Pull-based GitOps model and a traditional Push-based CI/CD pipeline?

❓ Q6: What are Sync Waves in ArgoCD, and how do they help manage complex multi-tier applications?

❓ Q7: How does drift detection work in a GitOps setup? What mechanisms monitor for changes?

❓ Q8: How does Auto Sync work in GitOps, and when would you choose to disable it in production?

❓ Q9: Imagine a bad deployment goes out via GitOps. How would you execute a rollback in ArgoCD?

❓ Q10: How do you scale GitOps configurations across multiple clusters in an enterprise environment?