From PR to Production: How Kubernetes Deployments Actually Work (Microservices in the Real World)

Most developers know how to write code. Fewer understand what actually happens after clicking “ Merge Pull Request .” And almost nobody truly understands what Kubernetes is doing during a production deployment — until something breaks. This post is a practical walkthrough of how code moves from PR → CI/CD → Helm → Kubernetes → Production, especially in a microservices setup. If you’ve ever shipped something that worked locally but behaved differently in production, this is for you. First: Kubernetes Doesn’t “Deploy” Your Code This mental model changes everything. Kubernetes doesn’t deploy applications the way we think about deployments. It maintains desired state . You declare: “I want 3 replicas.” “I want image order-service:1.4.2 .” “I want these resource limits.” Kubernetes continuously checks: Does current state match desired state? If not, it fixes it. That’s the entire system. Everything else — rolling updates, restarts, scaling — is just reconciliation. What Happens After You Me