How sieunhantanbao/sd2411_azure_infrastructure works
Based on our analysis of both the file tree and the README, this repository is focused on provisioning and managing a cloud-based microservices environment on Azure with strong CI/CD and monitoring integrations. In essence, it is an infrastructure and deployment repository that provides the Terraform scripts to provision Azure resources (AKS clusters, ACR, VMs), Helm chart manifests for deploying a multi-component application (frontend, backend, MongoDB) via ArgoCD, and additional tooling (Argo Rollouts, ArgoCD Image Updater, Istio, Prometheus, Grafana, and Jenkins integration) to support continuous deployment, blue/green strategies, and observability.
And lay out the major components
• Infrastructure Layer:
• Azure Kubernetes Service (AKS) that hosts the application workloads.
• Azure Container Registry (ACR) for storing Docker images.
• Virtual Machines (VMs) that support CI/CD (e.g., Jenkins) and other tooling.
• Deployment and CD Tools:
• ArgoCD with Helm support that monitors and deploys application manifests.
• ArgoCD Image Updater which automatically updates image tags.
• Argo Rollouts to implement blue/green or canary deployments.
• Application Layer:
• Microservices Application (referenced from sd2411_msa) with three major components:
• Backend service
• Frontend service
• MongoDB database
• CI Integration:
• Jenkins service running on VMs and linked (as noted in the reference repositories) to a shared library for performing CI tasks.
• Observability & Service Mesh Layer:
• Monitoring tools (Prometheus and Grafana) installed via provided scripts.
• Istio as the service mesh layer for traffic management and policy enforcement.
Relationships and Flow
• ArgoCD (and tools like Argo Rollouts and Image Updater) managing Helm chart deployments from the Helm directories (argocd/helm/prod and qa) into the AKS cluster.
• Relationship between the deployed applications (frontend, backend, database) and their dependencies.
• External integrations like Jenkins (from the sd2411_devops_ci repo), which watches for code changes, builds artifacts, and triggers deployments.
• Monitoring components (Prometheus and Grafana) as consuming data from the deployed workloads and relevant infrastructure.
• Optionally, include Istio if it is deployed, to emphasize its role in managing ingress/egress, routing, and traffic policies once the applications are running on AKS.
Architectural Patterns and Design Principles
• The design emphasizes Infrastructure as Code (Terraform) and GitOps (ArgoCD-driven deployments).
• Modular separation of environments (prod and qa directories under ArgoCD helm charts) illustrates environment-based configuration.
• Use of CI/CD pipelines (Jenkins, ArgoCD) indicates a continuous deployment strategy and automated infrastructure management.
• Separation between the deployment tooling (ArgoCD, Helm) and runtime components (AKS, microservices) is a key design principle.
Relevant Technologies
• Tools showcased include: Azure (AKS, ACR, VMs), Terraform, Kubernetes, Helm, ArgoCD (with Image Updater and Rollouts), Istio, Jenkins, Prometheus, and Grafana.
• That the Helm charts are organized per environment (prod, qa) and broken into subcomponents (backend, frontend, mongo).