Thoughts on Reading Gitops and Kubernetes
I recently read GitOps and Kubernetes, hoping to get a clear, structured guide on implementing GitOps in real projects.
While it wasn’t exactly what I expected, it made me reflect on how to develop devops skills.
Why I Read Gitops Book?
While many developers prefer video tutorials—they’re fast, visual, and great for following along. But videos delivers pre-digested answers; books force us to work through ideas ourselves. That’s why I still carve out time to read—it’s where deep understanding happens.
I picked it because I wanted a full picture—not just tool demos but real-world GitOps workflows.
The interest in DevOps comes from three key motivations:
What I Can Do – I enjoy infrastructure and architecture. Structuring systems feels like building with atomic components—everything has a purpose.
What I Like – Designing scalable, automated workflows aligns with my preference for logical, well-organized systems.
What the Industry Needs – GitOps isn’t just a trend; it’s becoming the way to manage cloud-native apps. And unlike niche AI models, these skills apply everywhere in tech.
At Least I Learnt Some?
Although the book wasn’t quite the hands-on manual I wanted. Instead of a step-by-step production guide, it introduced tools (Argo CD, Flux) and concepts (secrets, GitOps principles).
GitOps isn’t just tools—it’s a mindset (declarative infra, Git as truth).
Flux vs. Argo CD—each has trade-offs, and now I know when to use which.
Real-world challenges—like secret management and multi-cloud setups—aren’t just footnotes; they’re core to doing GitOps right.
What’s Next? Stop Reading, Start Building
At some point, you have to stop researching and start doing. So instead of hunting for the “perfect” guide, I’m going to:
Set up a real GitOps pipeline with Fluxcd.
Break it, fix it, and learn by failing.
Want to collaborate? If you’ve got a GitOps project or ideas, let’s build something together!
