--- tags: - devops - l1 - flashcard-deck - gitops --- [Portal](../../../../library/portal/index.md) | **Level:** [L1: Foundations](../../../../library/portal/levels.md) | **Topics:** [GitOps](../../../../library/portal/topics.md) | **Domain:** DevOps & Tooling id category difficulty tags question answer source_path gitops/11f3f287ccf9 gitops medium gitops, pull-request, sync What are some best practices for versioning in GitOps? Best practices include using meaningful commit messages, following branching strategies like Git Flow or Trunk-Based Development, and applying semantic versioning for the infrastructure and application code.\n\nExample: Semantic versioning for infra: v1.2.3 where major=breaking, minor=feature, patch=fix. Tag Helm charts and Terraform modules.\n\nGotcha: Avoid long-lived branches in GitOps repos — they cause merge conflicts and drift. Trunk-based development is preferred. projects/knowledge/interview/gitops/011-what-are-some-best-practices-for-versioning-in-git.txt gitops/2448f894d5fc gitops medium gitops, reconciliation How does GitOps support monitoring and observability? GitOps integrates monitoring tools like Prometheus, Grafana, or other observability tools to monitor the state of the system. It enables proactive alerting and observability, ensuring compliance with the desired state. projects/knowledge/interview/gitops/012-how-does-gitops-support-monitoring-and-observabili.txt gitops/2b3749754cb3 gitops hard gitops, multi-cluster, sync What are the challenges of implementing GitOps, and how can they be addressed? Challenges include complex deployment scenarios and handling large-scale infrastructure. Addressing these involves breaking down complex deployments into manageable units, ensuring thorough testing and automating error handling.\n\nExample: Challenge — managing 50 clusters across 3 clouds. Solution: use ApplicationSets (ArgoCD) or Kustomize overlays to template per-cluster config.\n\nGotcha: Secret management is the hardest GitOps challenge. Never store plaintext secrets in Git. projects/knowledge/interview/gitops/023-what-are-the-challenges-of-implementing-gitops-and.txt gitops/2c0b6e650f98 gitops hard gitops, rollback, sync What strategies are employed for disaster recovery in GitOps? GitOps employs strategies like repository backup, Git repository mirroring, and disaster recovery drills to ensure the rapid recovery of the desired system state in case of catastrophic events.\n\nExample: Mirror your GitOps repo to a secondary Git provider (GitHub to GitLab). Test DR quarterly by deploying from the mirror.\n\nRemember: GitOps DR = Git repo DR + cluster DR. If the repo is lost, you lose the desired state definition. projects/knowledge/interview/gitops/014-what-strategies-are-employed-for-disaster-recovery.txt gitops/377c1c642b07 gitops hard gitops, secrets, sync Discuss the role of GitOps in enabling DevSecOps practices. GitOps integrates security practices early in the development cycle, ensuring secure coding, access controls, and audit trails. It supports DevSecOps by automating security processes and incorporating security into CI/CD pipelines. projects/knowledge/interview/gitops/030-discuss-the-role-of-gitops-in-enabling-devsecops-p.txt gitops/42f56ce55e43 gitops medium gitops, helm, rollback, sync How does Helm support GitOps for managing Kubernetes applications? Helm organizes Kubernetes applications into 'charts,' making it easier to manage, package, and deploy these applications consistently across various environments. As the job of helm is to perform packaging, versioning, and managing Kubernetes applications. In a GitOps setup, Helm charts (declarative representations of Kubernetes resources) are versioned in Git, enabling automated deployments and rollbacks. projects/knowledge/interview/gitops/007-how-does-helm-support-gitops-for-managing-kubernet.txt gitops/44896c1075ba gitops medium gitops, rollback Describe the process of rollbacks in a GitOps environment. Rollbacks in GitOps are performed by reverting changes in the Git repository to a known good state. The CI/CD pipeline detects the changes and automatically rolls back the system state to the last known good state. projects/knowledge/interview/gitops/013-describe-the-process-of-rollbacks-in-a-gitops-envi.txt gitops/4e587a975fc5 gitops easy gitops, sync, reconciliation Explain how GitOps aligns with DevOps principles. GitOps embodies key DevOps principles like collaboration, automation, and continuous improvement. It aligns with the DevOps culture by enabling version control, automation, and collaboration in software development and deployment.\n\nRemember: GitOps is DevOps + Git as single source of truth. The key innovation: infrastructure changes go through the same PR review process as application code.\n\nName origin: Coined by Weaveworks in 2017. Alexis Richardson popularized the term. projects/knowledge/interview/gitops/029-explain-how-gitops-aligns-with-devops-principles.txt gitops/5377dbf35975 gitops hard gitops, sync Tell me about canary deployments and blue-green deployments in a GitOps context. In GitOps, canary and blue-green deployments are used for rolling out new versions gradually or switching traffic between different versions seamlessly. These deployment strategies are managed through Git, allowing controlled, automated deployments. projects/knowledge/interview/gitops/019-tell-me-about-canary-deployments-and-blue-green-de.txt gitops/5620c92fd61f gitops medium gitops, pull-request, sync Explain the role of pull requests in a GitOps workflow. Pull requests in GitOps serve as the mechanism for proposing changes to the desired system state. They go through review, ensuring changes are validated, and upon approval, are merged, triggering automated deployments. projects/knowledge/interview/gitops/010-explain-the-role-of-pull-requests-in-a-gitops-work.txt gitops/5cf9992c1b3e gitops easy gitops, sync, reconciliation What is GitOps, and how does it differ from traditional CI/CD? GitOps is like having a magic book that keeps track of how something should be done, and whenever you want things to be a certain way, you just follow the instructions in the book. Technically speaking, GitOps is a paradigm where the entire system state is versioned in a Git repository. It extends CI/CD by using Git as the source of truth for declarative infrastructure and application code, ensuring all changes are managed through version control and automated pipelines. projects/knowledge/interview/gitops/001-what-is-gitops-and-how-does-it-differ-from-traditi.txt gitops/6049d545937b gitops medium gitops, reconciliation How does GitOps support automated testing and validation? GitOps employs automated testing tools that run in the CI/CD pipeline, ensuring changes made to the system align with the desired state. Testing and validation are part of the continuous integration process. projects/knowledge/interview/gitops/028-how-does-gitops-support-automated-testing-and-vali.txt gitops/715d43bc4e0d gitops medium gitops, argocd, fluxcd, drift Discuss the automation strategies and tools used in GitOps. Automation strategies include CI/CD pipelines, Git hooks, and continuous reconciliation mechanisms. Tools like Jenkins, Flux, ArgoCD, and Ansible aid in automating the deployment and reconciliation processes.\n\nRemember: ArgoCD and FluxCD are the two dominant GitOps controllers. Both are CNCF projects.\n\nExample: ArgoCD for UI-driven teams, FluxCD for CLI/API-driven teams. Jenkins for build, ArgoCD for deploy. projects/knowledge/interview/gitops/027-discuss-the-automation-strategies-and-tools-used-i.txt gitops/79655af5af1b gitops hard gitops, sync, pull-request How does GitOps ensure compliance and auditability in the software delivery process? GitOps ensures compliance by maintaining a clear audit trail of all changes made to the system. By tracking changes through version control, it ensures compliance with policies and regulations.\n\nExample: Every kubectl apply in GitOps becomes a git commit with author, timestamp, and PR approval. Auditors can trace any change to a specific commit.\n\nRemember: Git log = audit trail. PR approvals = change control. Branch protection = enforcement. projects/knowledge/interview/gitops/021-how-does-gitops-ensure-compliance-and-auditability.txt gitops/94270a1b621f gitops easy gitops, drift, reconciliation, sync Explain the key benefits of adopting GitOps. GitOps ensures that everyone works from the same page, helping in maintaining consistency and control over software delivery. GitOps offers benefits like declarative configuration, version-controlled infrastructure, improved traceability, auditability, enhanced collaboration, and increased reliability through automated reconciliation. projects/knowledge/interview/gitops/002-explain-the-key-benefits-of-adopting-gitops.txt gitops/952df49a330f gitops hard gitops, reconciliation, drift, rollback How does GitOps handle potential conflicts in deployments? GitOps uses automated pipelines to detect and resolve conflicts. Changes made directly to the system are automatically reverted or reconciled with the desired state in the Git repository.\n\nExample: Engineer runs `kubectl scale deploy/api --replicas=5` directly. Next ArgoCD sync detects drift and reverts to the Git-declared 3 replicas.\n\nRemember: In GitOps, live state always converges to Git state. Manual changes are temporary by design. projects/knowledge/interview/gitops/024-how-does-gitops-handle-potential-conflicts-in-depl.txt gitops/9dece7d04cc1 gitops easy gitops, sync, drift, reconciliation Describe the GitOps workflow. GitOps uses Git for managing changes and updates to infrastructure and applications. It works in a way similar to how we manage different versions of documents or files. It sets up automatic mechanisms that ensure changes made in the Git repository are automatically applied to the systems, reducing manual intervention. In GitOps, the workflow involves developers making changes to the declarative configuration in Git, triggering a CI/CD pipeline. The changes are then automatically applied to the target environment through continuous deployment and reconciliation processes. projects/knowledge/interview/gitops/003-describe-the-gitops-workflow.txt gitops/b325889d167d gitops medium gitops, argocd, sync, fluxcd Compare Flux and ArgoCD for GitOps deployments. Both Flux and ArgoCD are GitOps tools for continuous deployment on Kubernetes. Flux focuses on automated reconciliation of the cluster state with Git, while ArgoCD offers a more user-friendly interface and application management capabilities. projects/knowledge/interview/gitops/008-compare-flux-and-argocd-for-gitops-deployments.txt gitops/b4774784d32e gitops hard gitops, secrets, pull-request Discuss the role of GitOps in enforcing security policies and access control. GitOps enforces security policies by enabling RBAC (Role-Based Access Control) for managing access to Git repositories and CI/CD pipelines. It ensures that only authorized users can make changes to the system state. projects/knowledge/interview/gitops/022-discuss-the-role-of-gitops-in-enforcing-security-p.txt gitops/c708e44198c0 gitops hard gitops, secrets Explain GitOps best practices for managing secrets and sensitive information. Best practices include storing secrets in a secure, encrypted manner using tools like Vault or Kubernetes secrets, and utilizing secret management solutions that ensure sensitive data is never exposed in the Git repository. projects/knowledge/interview/gitops/018-explain-gitops-best-practices-for-managing-secrets.txt gitops/c861d2bf8da5 gitops medium gitops, secrets, pull-request How does GitOps ensure security and compliance in software delivery? GitOps ensures that any modifications or updates are done through a controlled and traceable process, reducing the risk of unauthorized changes.\nWith version control, GitOps maintains records of all changes, aiding in audits and compliance checks. GitOps promotes security by ensuring that all changes are traceable, auditable, and consistently applied through automated pipelines. Policies, configurations, and access controls can be enforced within Git, ensuring compliance and minimizing human errors. projects/knowledge/interview/gitops/004-how-does-gitops-ensure-security-and-compliance-in-.txt gitops/d6f9e202de1a gitops medium gitops, drift, reconciliation, sync How does GitOps handle configuration drift or divergence from the desired state? GitOps continuously reconciles the actual system state with the declared configuration stored in Git. In case of drift, the automated reconciliation process ensures that the system state is always aligned with the desired state. projects/knowledge/interview/gitops/016-how-does-gitops-handle-configuration-drift-or-dive.txt gitops/d8ab4341b9e7 gitops easy gitops, pull-request How does GitOps leverage version control for managing deployments? By using version control, GitOps ensures that every change made is recorded, enabling a consistent and organized management of updates and deployments.\nGitOps uses version control to manage infrastructure and application code. All changes are made through pull requests, reviewed, versioned, and audited, ensuring that the entire system state is captured and trackable. projects/knowledge/interview/gitops/009-how-does-gitops-leverage-version-control-for-manag.txt gitops/dd3a500fff88 gitops easy gitops, argocd, fluxcd, helm What tools are commonly used in a GitOps workflow? Git as the source of truth, along with tools like Kubernetes for orchestration, Helm for package management, Flux or ArgoCD for deployment automation, and other CI/CD tools like Jenkins or GitLab for the pipeline. projects/knowledge/interview/gitops/005-what-tools-are-commonly-used-in-a-gitops-workflow.txt gitops/e9344ddea30c gitops medium gitops, pull-request How does GitOps facilitate collaboration among teams? GitOps encourages collaboration by allowing all team members to contribute to the system's state using Git's branching and pull request mechanisms. It ensures transparency, auditability, and traceability in the development and deployment process. projects/knowledge/interview/gitops/017-how-does-gitops-facilitate-collaboration-among-tea.txt gitops/eb4b53167c99 gitops medium gitops, drift, reconciliation Explain the role of observability in GitOps. Observability in GitOps involves using tools to collect and analyze metrics, logs, and events to understand the system's behavior. It aids in proactive troubleshooting, optimizing performance, and ensuring the desired system state is maintained. projects/knowledge/interview/gitops/025-explain-the-role-of-observability-in-gitops.txt gitops/f2cb5490b76b gitops medium gitops, kustomize, helm Explain the relationship between GitOps and Infrastructure as Code (IaC). GitOps relies on Infrastructure as Code principles to define and manage infrastructure configuration and application deployment. Infrastructure and application configuration are versioned in Git, ensuring automation and reproducibility.\n\nExample: Terraform for infrastructure provisioning, Helm charts for K8s deployment, both stored in Git. GitOps applies the same version-control discipline to ops.\n\nRemember: IaC = declarative infrastructure definitions. GitOps = IaC + automated reconciliation + Git as source of truth. projects/knowledge/interview/gitops/015-explain-the-relationship-between-gitops-and-infras.txt gitops/f6e04afc8589 gitops easy gitops, reconciliation, drift, sync Explain the role of Kubernetes in a GitOps setup. Kubernetes manages and orchestrates the applications and services, ensuring they run smoothly and consistently across different environments. In technical terms Kubernetes serves as the container orchestration platform, providing the infrastructure where applications are deployed and managed. GitOps leverages Kubernetes to ensure the desired state is continuously reconciled with the declared configuration stored in Git. projects/knowledge/interview/gitops/006-explain-the-role-of-kubernetes-in-a-gitops-setup.txt gitops/f7e6804a56da gitops medium gitops, drift, reconciliation How can monitoring and alerting be integrated into a GitOps workflow? Monitoring tools like Prometheus or Grafana can be integrated into the GitOps workflow to capture performance metrics, visualize data, and trigger alerts based on predefined thresholds or anomalies.\n\nExample: Prometheus alerts on sync failures, Grafana dashboards showing deployment frequency and rollback rate. ArgoCD has built-in Prometheus metrics.\n\nGotcha: Monitor the GitOps controller itself — if ArgoCD goes down, drift goes undetected. projects/knowledge/interview/gitops/026-how-can-monitoring-and-alerting-be-integrated-into.txt gitops/fb687d841a86 gitops medium gitops, rollback Explain progressive delivery and how it's achieved in GitOps. Progressive delivery in GitOps involves gradually exposing features to users, allowing gradual testing and rollback capabilities. GitOps enables this through version control and controlled rollouts managed by CI/CD processes.\n\nExample: Flagger (by Weaveworks) automates canary releases in GitOps: deploys canary, monitors metrics, promotes or rolls back automatically.\n\nRemember: Progressive delivery tools: Flagger, Argo Rollouts. Both integrate with Istio/Linkerd for traffic splitting. projects/knowledge/interview/gitops/020-explain-progressive-delivery-and-how-its-achieved-.txt gitops/train-lab07-a gitops medium gitops, drift, training What is configuration drift in a GitOps context? Config drift occurs when the live cluster state diverges from the declared state in Git. Causes: manual kubectl edits, hotfixes applied directly, or controllers modifying resources. ArgoCD detects this as 'OutOfSync'. Fix by either codifying the change in Git or syncing to revert. training/interactive/runtime-labs/lab-runtime-07-gitops-sync-and-drift/ gitops/train-lab07-b gitops hard gitops, argocd, training How do you reconcile drift without losing a production hotfix? 1) Diff live state vs declared state (helm get manifest vs kubectl get); \n2) If the drift was intentional (hotfix), codify it in values/manifests and commit to Git; \n3) If accidental, trigger a sync to revert; \n4) Set up admission webhooks or RBAC to prevent direct changes. training/interactive/runtime-labs/lab-runtime-07-gitops-sync-and-drift/ gitops/train-lab05-a gitops easy gitops, helm, training What does 'helm rollback grokdevops 0' do? Revision 0 means 'roll back to the previous revision'. Helm restores the values and templates from the last successful release. Combined with --wait, it ensures pods are healthy before returning. This is the fastest recovery from a bad upgrade. training/interactive/runtime-labs/lab-runtime-05-helm-upgrade-rollback/ --- ## Wiki Navigation ### Related Content - Argo Flashcards *(CLI)* (flashcard_deck, L1) — GitOps - [GitOps](../../../../library/topics/gitops/index.md) (Topic Pack, L1) — GitOps - [GitOps & ArgoCD Drills](../../../../library/drills/gitops_argocd_drills.md) (Drill, L2) — GitOps - [Interview: Config Drift Detected](../../../../library/interview-scenarios/07-config-drift-detected.md) (Scenario, L2) — GitOps - [Interview: GitOps Drift Detected](../../../../library/interview-scenarios/16-gitops-drift-detected.md) (Scenario, L2) — GitOps - Lab: GitOps Sync and Drift *(CLI)* (Lab, L2) — GitOps - [Runbook: ArgoCD Out of Sync](../../../../library/runbooks/cicd/argocd_out_of_sync.md) (Runbook, L2) — GitOps - [Runbook: Deploy Rollback](../../../../library/runbooks/cicd/deploy-rollback.md) (Runbook, L1) — GitOps - [Skillcheck: GitOps](../../../../library/skillchecks/gitops.skillcheck.md) (Assessment, L2) — GitOps - [Track: Helm & Release Ops](../../../../library/curriculum/tracks/helm_and_release_ops.md) (Reference, L1) — GitOps