GitOps at scale with ArgoCD App of Apps. Organize applications by projects (devops, observability, frontend, backend). Deploy internal or external Helm charts via git - just add the reference, commit, and ArgoCD syncs. Zero manual kubectl operations.

Get a complete Kubernetes stack with observability in minutes:

# 1. Install ArgoCD cd bootstrap ./bootstrap.sh argocd # 2. Configure GitHub Access ./bootstrap.sh configure-github # 3. Deploy Root Manifest (deploys all applications automatically) kubectl apply -f argocd-manifest/root-manifest.yaml

That's it! ArgoCD will automatically deploy:

• ✅ cert-manager (SSL/TLS certificates)
• ✅ ingress-nginx (Ingress controller)
• ✅ metrics-server (Resource metrics)
• ✅ SigNoz (Complete observability: APM, Logs, Metrics, Traces)
• ✅ k8s-infra (Kubernetes logs & metrics collection)

This repository implements a scalable GitOps workflow using:

• ArgoCD for continuous deployment
• Helm for package management
• App of Apps pattern for managing dozens of applications
• Project-based organization for clean separation of concerns

root-manifest (App of Apps) ├── devops (Project) │ ├── cert-manager # SSL/TLS certificate management │ ├── ingress-nginx # Ingress controller │ ├── metrics-server # Kubernetes metrics API │ ├── signoz # Observability platform (APM, metrics, traces) │ └── k8s-infra # Kubernetes logs & metrics collection └── frontend (Project) ├── app1 └── app2 

. ├── argocd-manifest/ # Helm chart that generates ArgoCD resources │ ├── Chart.yaml │ ├── values.yaml # Root configuration - enables/disables projects │ ├── root-manifest.yaml # Bootstrap file to deploy to ArgoCD │ └── templates/ │ ├── projects.yaml # Generates AppProjects │ ├── applications.yaml # Generates Applications │ └── applicationsets.yaml # Generates ApplicationSets ├── projects/ # Project-based organization │ ├── devops/ │ │ ├── root.yaml # Defines devops project + all tools │ │ ├── cert-manager/ │ │ │ └── values.yaml # Cert-manager helm values │ │ ├── ingress-nginx/ │ │ │ └── values.yaml # Ingress-nginx helm values │ │ ├── metrics-server/ │ │ │ └── values.yaml # Metrics-server helm values │ │ ├── signoz/ │ │ │ └── values.yaml # SigNoz observability platform │ │ └── k8s-infra/ │ │ └── values.yaml # K8s logs & metrics collection │ └── frontend/ │ ├── root.yaml # Defines frontend project + all apps │ └── app1/ │ └── values.yaml ├── charts/ # Custom Helm charts (optional) ├── bootstrap/ # Bootstrap scripts │ ├── bootstrap.sh │ └── components/ │ ├── argocd.sh │ └── configure-github.sh └── config.env # Configuration 

When you run kubectl apply -f argocd-manifest/root-manifest.yaml:

1. Root Manifest Application is created in ArgoCD
2. Root manifest reads argocd-manifest/values.yaml and creates Project Applications
3. Each Project Application reads its projects/<project>/root.yaml
4. Each root.yaml creates the AppProject and all its child ApplicationSets
5. ApplicationSets generate individual Applications for each tool
6. ArgoCD syncs everything automatically using GitOps 🎉

1. Root Level (argocd-manifest/values.yaml):

   Applications: devops: enable: true # Enable/disable entire project valueFiles: - $values/projects/devops/root.yaml

2. Project Level (projects/devops/root.yaml):

   Projects: devops: enable: true description: DevOps tools ApplicationSets: cert-manager: enable: true # Enable/disable individual app chartVersion: v1.13.2 valueFiles: - $values/projects/devops/cert-manager/values.yaml

3. Application Level (projects/devops/cert-manager/values.yaml):

   installCRDs: true replicaCount: 1 resources: limits: cpu: 100m

1. Create values directory:

   mkdir -p projects/devops/my-new-tool

2. Create values file:

   cat > projects/devops/my-new-tool/values.yaml <<EOF # My tool helm values replicaCount: 1 EOF

3. Add to project's root.yaml:

   ApplicationSets: my-new-tool: enable: true syncWave: 4 name: my-new-tool project: devops namespace: my-new-tool generators: - list: elements: - cluster: in-cluster url: https://kubernetes.default.svc chartVersion: 1.0.0 sources: - chart: my-new-tool repoURL: https://charts.example.com targetRevision: '{{.chartVersion}}' helm: valueFiles: - $values/projects/devops/my-new-tool/values.yaml - repoURL: git@github.com:adiii717/k8s-gitops.git targetRevision: main ref: values

4. Commit and push - ArgoCD syncs automatically!

1. Create project structure:

   mkdir -p projects/backend

2. Create root.yaml:

   cat > projects/backend/root.yaml <<EOF global:  argocdNamespace: argocd  Projects:  backend:  enable: true  syncWave: -1  name: backend  description: Backend services  destinations:  - namespace: '*'  server: https://kubernetes.default.svc  sourceRepos:  - '*'  Applications:  api-service:  enable: true  syncWave: 1  name: api-service  namespace: backend  project: backend  sources:  - repoURL: git@github.com:adiii717/k8s-gitops.git  targetRevision: main  path: charts/api-service  helm:  valueFiles:  - $values/projects/backend/api-service/values.yaml  - repoURL: git@github.com:adiii717/k8s-gitops.git  targetRevision: main  ref: values EOF

3. Enable in root manifest (argocd-manifest/values.yaml):

   Applications: backend: enable: true syncWave: 102 name: backend sources: - repoURL: git@github.com:adiii717/k8s-gitops.git targetRevision: main ref: values - repoURL: git@github.com:adiii717/k8s-gitops.git targetRevision: main path: argocd-manifest helm: releaseName: backend valueFiles: - $values/projects/backend/root.yaml

Edit config.env:

# ArgoCD Configuration ARGOCD_NAMESPACE=argocd ARGOCD_CHART_VERSION=5.51.4 # GitHub Configuration GITHUB_REPO_URL=git@github.com:adiii717/k8s-gitops.git GITHUB_SSH_KEY_PATH=~/.ssh/id_ed25519 # GitOps Configuration ARGOCD_MANIFEST_PATH=argocd-manifest ROOT_MANIFEST_NAME=root-manifest PROJECTS_PATH=projects

# Get password cat .env # Port forward kubectl port-forward svc/argocd-server -n argocd 8080:443 # Access at https://localhost:8080 # Username: admin # Password: (from .env)

✅ Scalable: Add dozens of applications by just adding values files

✅ Project-Based: Clean separation (devops, frontend, backend, etc.)

✅ Hierarchical: Three-level structure (Root → Project → Application)

✅ Version Control: Chart versions defined in root.yaml

✅ Enable/Disable: Toggle entire projects or individual apps

✅ Sync Waves: Control deployment order with syncWave

✅ Multiple Sources: Support for Helm repos and Git repos

✅ ApplicationSets: Parameterize deployments across environments

Control deployment order:

syncWave: 1 # Deploy first syncWave: 2 # Deploy second syncWave: 3 # Deploy third

Deploy same app to multiple clusters/environments:

ApplicationSets: my-app: generators: - list: elements: - cluster: dev url: https://dev-cluster chartVersion: 1.0.0 - cluster: prod url: https://prod-cluster chartVersion: 1.0.1

Place custom Helm charts in charts/ directory and reference them:

sources: - repoURL: git@github.com:adiii717/k8s-gitops.git targetRevision: main path: charts/my-custom-app

# Remove all ArgoCD resources bash ~/devops/scripts/cleanup-argocd.sh

Follow Semantic Commit Messages:

feat(devops): add prometheus monitoring fix(frontend): resolve nginx configuration docs(readme): update installation steps chore(deps): bump cert-manager to v1.14 

kubectl get applications -n argocd kubectl describe application <app-name> -n argocd

kubectl get appprojects -n argocd

kubectl patch application <app-name> -n argocd \ --type merge -p '{"operation":{"initiatedBy":{"username":"admin"},"sync":{"revision":"main"}}}'

1. Enable Gradually: Start with enable: false, test, then enable
2. Use Sync Waves: Define clear deployment order
3. Version Everything: Pin chart versions in root.yaml
4. Small Commits: One app/change per commit
5. Test Locally: Use helm template to validate before committing
6. Document Values: Comment your values files

Current production applications:

kubectl port-forward -n platform svc/signoz 3301:8080 # Open: http://localhost:3301

SigNoz over Prometheus/Grafana/Jaeger:

• ✅ Unified platform: Metrics, Logs, Traces, APM in one UI
• ✅ Lower operational overhead: Single deployment vs 4+ tools
• ✅ Better performance: ClickHouse is faster than traditional TSDB
• ✅ OpenTelemetry native: Future-proof observability
• ✅ Cost-effective: No separate storage for logs/traces/metrics

Created with ❤️ by adilm717@gmail.com

Built for freelance Kubernetes infrastructure projects. Feel free to use it, fork it, and adapt it for your needs.

If you find this repository helpful:

• ⭐ Star it on GitHub
• 🔀 Fork it and customize for your infrastructure
• 💬 Reach out for consulting or collaboration

Philosophy: Clean, scalable, production-ready GitOps that's easy to understand and extend.