How danarbiv/gitops-certification-examples works
Main Components
a. GitOps Control Plane:
• ArgoCD Controller (shown from argocd-noauth directory)
• Argo Rollouts Controller (from argo-rollouts-controller)
• Sealed Secrets Controller (from bitnami-sealed-controller)
b. Application Deployment Patterns:
• Blue-Green Deployments (from blue-green-app)
• Canary Deployments (from canary-app and canary-app-timed)
• Basic Deployments (from simple-app)
c. Configuration Management Approaches:
• Helm Charts (from helm-app and ambassador-chart)
• Kustomize Overlays (from kustomize-app)
• Declarative Manifests (from declarative directory)
Relationship Flows
Git Repository
• ↓
ArgoCD Controller
• ↓
Deployment Strategies
• → Blue/Green
• → Canary
• → Simple Deployments
• ↓
Kubernetes Cluster
Specific Elements
a. Security Layer:
• Sealed Secrets controller integration
• Secret management flow (from secret-app)
b. Configuration Management:
• Three parallel paths: Helm, Kustomize, and raw manifests
• Environment overlays (production/staging)
Important Details to Capture
• Ambassador API Gateway configuration (from ambassador-chart)
• Progressive Delivery patterns
• Environment-specific configurations
• Secret management workflow
┌─ Source Control ─┐ ┌─ GitOps Controllers ─┐ ┌─ Deployment Patterns ─┐
• Git Repository │ → │ ArgoCD │ → │ - Blue/Green │
• ┘ │ Argo Rollouts │ │ - Canary │
• Sealed Secrets │ │ - Simple │
• ┘ └────────────────────┘
• ↓ ↓
• ┌─ Config Management ──┐ ┌─ Target Platform ───┐
• Helm │ → │ Kubernetes Cluster │
• Kustomize │ └──────────────────┘
• Raw Manifests │
• ┘