How gunjanrajsingh/nike-landing-page-argocd works
Project Type and Purpose
• This is a single-page React application (built with Vite and Tailwind) packaged in a Docker container and deployed to Kubernetes via Argo CD and Helm.
• The “Sample project for ArgoCD” README confirms that the focus is on demonstrating a GitOps-driven CI/CD flow.
File-Structure Analysis
• Top-level CI/CD/config files:
• azure-pipelines.yml – Azure DevOps pipeline definition
• ArgoCD.yml and argo/argo-application.yaml – Argo CD Application manifests
• Dockerfile – containerizes the front-end app
• helm-chart/… – Helm Chart for templating Deployment and Service
• templates/… – (likely a secondary or example manifest set)
• Frontend code under src/: standard Vite+React layout with assets, components, sections
• Configuration: package.json, vite.config.js, tailwind.config.js, .eslintrc.cjs
Key System Components
a. Code Repository
• Contains application source, Dockerfile, Helm Chart, Argo CD manifests, pipeline definitions.
b. CI Pipeline (Azure DevOps)
• Pulls code, builds container image, pushes to Container Registry.
c. Container Registry (e.g., Azure ACR or Docker Hub)
• Hosts the tagged frontend image.
d. GitOps controller (Argo CD)
• Watches the Git repo/manifests, synchronizes Application to the cluster.
e. Kubernetes Cluster
• Receives Helm-rendered Deployment and Service resources.
• Deployment pods serve static build via an HTTP server (e.g., Nginx).
f. End Users
• Browse to the LoadBalancer/Ingress to consume the static front-end.
Relationships and Interactions
• Azure Pipelines triggers on commit → builds Docker image → pushes to Registry → updates image tag in Helm values (manually or via pipeline step).
• GitOps: Argo CD monitors Git (helm-chart/values.yaml or argo/argo-application.yaml) → detects manifest change → deploys updated Deployment to K8s.
• Kubernetes Service exposes pods, optionally behind Ingress.
• End Users’ HTTP requests flow through Service → Pod → React static assets.
Architectural Patterns & Principles
• GitOps: manifests-as-code, automated sync via Argo CD
• Immutable containers: Docker image tags in source
• Declarative infrastructure: Helm Chart templates + values
• Clear separation: CI pipeline vs. GitOps delivery