Why I’m starting Cloud Native Field Notes
Cloud native work rarely fails because someone forgot what a Pod is. It fails in the gaps: ownership between platform and app teams, GPU capacity that looks healthy but sits idle, traffic contracts that live in Ingress folklore, observability that nobody owns end-to-end.
Cloud Native Field Notes is my series for that layer — practical writing on Kubernetes, platform engineering, DevOps, and the CNCF community. Not another beginner tutorial stream. Notes from shipping, operating, and learning in public.
What the series covers
Expect a mix of:
- Platform & operations — paved roads, Gateway API, GitOps maturity, day-two reliability
- AI infrastructure on Kubernetes — inference, accelerators, cost, and what platform teams actually own
- Observability & delivery — OpenTelemetry, SLOs, change safety
- Community & contribution — SIGs, KCDs, mentorship, and conversations with practitioners (including conference hallway tracks when they teach something transferable)
How I’ll write
Every post aims for a decision, not a tour. If a piece cannot answer “what should a platform or DevOps team do differently on Monday?”, it isn’t done.
Canonical articles live on blog.ramneekkalra.in. LinkedIn is the megaphone. YouTube is where longer conversations live.
What I’m not doing
- Vendor roundups disguised as education
- Tutorial spam that already exists in official docs
- Chasing CNCF blog placement on day one
Earn the bigger stages with a trail of useful writing first. That’s the plan for Field Notes.