SHSanskriti Harmukhinvultr.hashnode.dev·1d ago · 8 min readSetting Up Argo CD on KubernetesArgo CD is a Kubernetes-native, declarative GitOps tool for deploying applications at scale. It pulls application manifests directly from a Git repository and syncs them to a Kubernetes cluster, suppo00
NTNhật Trườnginblog.nh4ttruong.me·4d ago · 3 min readOne Argo CD Hub, Many Clusters, No TicketsAt most organizations, shipping an application to an environment means a Developer files a ticket, waits for the DevOps team, then verifies. The same flow repeats for a version bump, a health check po00
TCThankGod Chibugwum Oboboinactocodes.hashnode.dev·5d ago · 12 min readGitOps in Practice: How to Manage Kubernetes State with ArgoCD and HelmKubernetes configuration drift is a silent killer of operational confidence. A developer applies a quick fix directly with kubectl during an incident. A CI pipeline pushes an update that partially app00
LBLalit Baggainblog.lalitbagga.com·Sep 3 · 7 min readArgo CD Fixed My Drift, Then Deployed My Bad ReleaseThis project started with a simple goal: run Kubernetes without keeping an EKS cluster online every day. In I Wanted Kubernetes Without an Always-On EKS Bill, I built an always-on k3s lab on my home s00
SKSanjeev Kumar Bharadwajinblog.nyzex.in·Sep 3 · 10 min readGitOps Is Not Deployment Automation: Where the Abstraction Actually Breaks GitOps is often introduced as a clean operational model in which Git stores the desired state of a system and a controller continuously reconciles the running environment against that state. In Kubern00
SSunnyinsunny-snskarora.hashnode.dev·Aug 30 · 7 min read📜 HomeLab Chronicles: Episode 6 - Source of TruthHey all 👋 Last episode a power cut exposed an uncomfortable fact: my cluster's entire memory lived in one SQLite-flavored database, on one laptop, bound to one Wi-Fi address, guarded by one aging bat00
GFGuilherme Ferreiraingferreir.hashnode.dev·Aug 28 · 12 min readOpenShift application Day-2: 7 guardrails that refuse the bad state in GitThe problem that troubleshooting does not solve Part 2 delivered a runbook of ten commands. The team knows how to diagnose a CrashLoop, how to tell a 503 from a 502 on the Route, and that oc logs --pr00
LBLalit Baggainblog.lalitbagga.com·Aug 27 · 8 min readThe Rollback Worked. My Next Deploy Could Break It Again.My application was working again. That should have been the end of the problem. It was not. In [the first article in this series(https://blog.lalitbagga.com/posts/why-i-chose-k3s-debian-homelab), I bu00
GFGuilherme Ferreiraingferreir.hashnode.dev·Aug 26 · 13 min readOpenShift Application Day-2: 7 Mistakes That Take Down the Service, Not the ClusterThe first oc apply in the namespace usually passes. The Route responds, the pod reaches Running, and the pipeline turns green. Everything works — until the Route certificate expires with no warning, t00
KGKunal Guptainkunalforked.hashnode.dev·Aug 18 · 7 min readWhen 50 Jobs Show Up at OncePrefect concurrency limits and queue priority, explained the simple way Continuation of Prefect on Kubernetes: Explained Like You're Five, that post covered one job turning into one pod. This one's ab10
