How jnayak1482/kind_github_argocd works
Project type and purpose
• This is a single-page React application (built with Create React App) delivering a frontend UI.
• It’s containerized via Docker and deployed into a Kubernetes cluster via GitOps (Argo CD), using Metallb for LoadBalancer functionality.
File structure
• Top levels:
• Dockerfile + .dockerignore → how the React app is containerized.
• manifest/ → holds Kubernetes resources (Argocd App, Deployment, Service, Kustomization, Metallb config).
• public/ + src/ → React app source code.
• package.json / lock → Node dependencies & scripts.
• No backend code here; this is purely a frontend micro-service.
Key README insights
• Standard Create React App lifecycle: npm start, build, test, eject.
• No custom architecture described beyond React’s default.
Main components
a. Browser (end-user)
b. Container registry (optional)
c. Kubernetes cluster
• Argo CD server (GitOps controller)
• React-app Deployment (Pods running Nginx or node server serving static build)
• Service (ClusterIP)
• Metallb LoadBalancer (external IP for the Service)
d. Git repository (source of manifests & Dockerfile)
Relationships & data flows
• Developer pushes code & manifests to Git repo →
Argo CD sees commit →
Argo CD syncs manifests →
Kubernetes Deployment updated →
New pods built (pull image from registry) →
Metallb assigns external IP to Service →
User’s browser loads static assets via that external IP over HTTP/S.
Architectural patterns & principles
• GitOps for continuous deployment (Argo CD driving cluster state from Git).
• Containerization of frontend static assets.
• Separation of concerns: UI code (src/, public/) vs. infra code (manifest/).
Technologies & frameworks
• React (frontend library)
• Create React App (build toolchain: Webpack, Babel)
• Docker (containerization)
• Kubernetes (orchestration)
• Argo CD (GitOps controller)
• Metallb (bare-metal LoadBalancer)