Day 8 | Kustomize ConfigMapGenerator with ArgoCD | Manage Environment Variables in Kubernetes

🚀 Welcome to Day 6 of the GitOps with ArgoCD series! In this hands-on session, we continue our journey with Kustomize and learn how to manage environment-specific configuration using ConfigMapGenerator — and then deploy those changes automatically through ArgoCD. In previous sessions, we learned how Kustomize uses Base + Overlays to manage Kubernetes manifests without complex templating. Today, we'll take that one step further and see how to manage application configuration such as database hostname, database port, and Spring profiles. 🔥 What you'll learn 🔹 What is ConfigMapGenerator in Kustomize 🔹 Difference between a plain Kubernetes ConfigMap and ConfigMapGenerator 🔹 Managing environment-specific configuration with Kustomize 🔹 Using config.properties with ConfigMapGenerator 🔹 Injecting ConfigMap values into a Kubernetes Deployment 🔹 Understanding Kustomize's automatically generated ConfigMap hash 🔹 How ConfigMap changes can trigger Kubernetes Pod rollouts 🔹 Using Kustomize with ArgoCD 🔹 GitOps flow: Git → ArgoCD → Kustomize → Kubernetes 🔹 Enabling ArgoCD Auto-Sync for configuration changes 🔹 Verifying the generated ConfigMap and Deployment from the ArgoCD UI 🏗️ Architecture Git Repository ⬇️ Kustomize Base + SIT Overlay ⬇️ ConfigMapGenerator ⬇️ ArgoCD Auto-Sync ⬇️ Kubernetes Deployment + ConfigMap The important concept we'll see is: ConfigMap content changes → new ConfigMap name/hash → Deployment reference changes → Kubernetes performs a rolling update. 📂 GitHub Repository: sehstudents-config GitHub Repository 📚 Official Kustomize Documentation: Kustomize Documentation 🔴 ArgoCD Documentation: Argo CD Documentation If you're learning Kubernetes, Kustomize, GitOps and ArgoCD, this session will help you understand how environment-specific configuration can be managed cleanly and deployed automatically. 👍 Like 💬 Share your questions 🔔 Subscribe for upcoming videos Thanks for watching and happy learning! 🚀