Bird
0
0

Which Git repository structure is recommended for ArgoCD to manage multiple Kubernetes applications?

easy📝 Conceptual Q2 of 15
Kubernetes - Advanced Deployment Patterns
Which Git repository structure is recommended for ArgoCD to manage multiple Kubernetes applications?
AA repository with binary files of Kubernetes manifests
BMultiple repositories with all manifests mixed in one folder
CA single repository with separate folders for each application
DA repository containing only Helm charts without any manifests
Step-by-Step Solution
Solution:

  1. Step 1: Identify best Git repo structure for ArgoCD

    Using one repo with separate folders per app helps ArgoCD track and sync each app cleanly.

  2. Step 2: Evaluate other options

    Multiple repos or mixing manifests cause complexity; binary files are not readable; Helm charts alone may be used but manifests are needed.

  3. Final Answer:

    A single repository with separate folders for each application -> Option C

  4. Quick Check:

    Repo structure = Separate folders per app [OK]
Quick Trick: Keep apps in separate folders inside one Git repo [OK]
Common Mistakes:
  • Mixing all manifests in one folder
  • Using binary files instead of YAML
  • Ignoring folder structure for apps

Want More Practice?

15+ quiz questions · All difficulty levels · Free

Free Signup - Practice All Questions
More Kubernetes Quizzes
Advanced Deployment Patterns - Canary deployments - Quiz 7medium Helm Package Manager - Upgrading and rolling back releases - Quiz 10hard Monitoring and Logging - Why cluster monitoring matters - Quiz 9hard Production Best Practices - Cost optimization in Kubernetes - Quiz 8hard RBAC and Security - Roles and ClusterRoles - Quiz 11easy RBAC and Security - Why RBAC matters in Kubernetes - Quiz 2easy RBAC and Security - Pod security standards - Quiz 12easy Service Mesh - Service mesh vs library-based approach - Quiz 13medium Service Mesh - Istio overview - Quiz 1easy Service Mesh - Service mesh vs library-based approach - Quiz 6medium