Are you a Node.js + Express developer who understands Docker and Linux, but feels overwhelmed by Kubernetes? This guide is for you. We are going to transition from standard Docker to Kubernetes step-by-step.<\/p>\n\n\n\n
We are deploying a very simple Node.js + Express application packaged into a Docker image called Traditionally, you would run Docker containers directly on Linux servers with a Load Balancer in front. graph TD LB[Load Balancer] –> S1[Server 1\\nmyapp:v1] LB –> S2[Server 2\\nmyapp:v1]<\/p>\n\n\n\n The Problem:<\/strong> Kubernetes is an orchestration tool that automates the deployment, scaling, and management of containers.<\/p>\n\n\n\n When deployed on Kubernetes with If Worker 2 crashes, Kubernetes automatically fixes it without manual intervention.<\/p>\n\n\n\n Scaling is just changing a number in your Deployment manifest. Set Understanding how the hardware maps to Kubernetes concepts: graph TD PS[Physical Server] –> WN[Worker Node\\nK8s Managed] WN –> P1[Pod-1\\nLogical Wrapper] P1 –> C1[Container\\nmyapp:v1] WN –> P2[Pod-2] P2 –> C2[Container\\nmyapp:v1]<\/p>\n\n\n\n Tracing a request from the user to your Express code: flowchart TD A[Browser] –>|URL| B{Service} B –>|Load balances| C[Pod\\nNode-2, Port 3000] C –>|Forwards| D[Container] D –>|app.get| E[Express Route] E –>|Response| A<\/p>\n\n\n\n Kubernetes can automatically scale your application up and down based on traffic using a Horizontal Pod Autoscaler (HPA)<\/strong>.<\/p>\n\n\n\n To make autoscaling work, you need three things:<\/p>\n\n\n\n Pro Tip:<\/strong> By keeping the HPA in a separate file (e.g., If you have Docker and Minikube installed, you can try this exact setup yourself!<\/p>\n\n\n\n 1. Start the cluster and build the image:<\/strong><\/p>\n\n\n\n 2. Deploy to Kubernetes:<\/strong><\/p>\n\n\n\n 3. Test the Load Balancer (v2)<\/strong> Want to see the autoscaler in action? Open three terminal windows to watch the magic happen:<\/p>\n\n\n\n The Cooldown Period:<\/strong> Node.js is incredibly fast. To force a scaling event, you might need to temporarily lower your HPA target to If you are familiar with Docker Compose, Minikube commands will feel very similar:<\/p>\n\n\n\n <\/p>\n","protected":false},"excerpt":{"rendered":" Kubernetes for Express Developers: A Beginner-Friendly Guide Are you a Node.js + Express developer who understands Docker and Linux, but feels overwhelmed by Kubernetes? This guide is for you. We are going to transition from standard Docker to Kubernetes step-by-step. The Application We are deploying a very simple Node.js + Express application packaged into a […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":[],"categories":[20],"tags":[],"_links":{"self":[{"href":"https:\/\/codeinsightacademy.com\/blog\/wp-json\/wp\/v2\/posts\/2985"}],"collection":[{"href":"https:\/\/codeinsightacademy.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/codeinsightacademy.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/codeinsightacademy.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/codeinsightacademy.com\/blog\/wp-json\/wp\/v2\/comments?post=2985"}],"version-history":[{"count":4,"href":"https:\/\/codeinsightacademy.com\/blog\/wp-json\/wp\/v2\/posts\/2985\/revisions"}],"predecessor-version":[{"id":2989,"href":"https:\/\/codeinsightacademy.com\/blog\/wp-json\/wp\/v2\/posts\/2985\/revisions\/2989"}],"wp:attachment":[{"href":"https:\/\/codeinsightacademy.com\/blog\/wp-json\/wp\/v2\/media?parent=2985"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/codeinsightacademy.com\/blog\/wp-json\/wp\/v2\/categories?post=2985"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/codeinsightacademy.com\/blog\/wp-json\/wp\/v2\/tags?post=2985"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}myapp:v1<\/code>.<\/p>\n\n\n\nconst express = require(\"express\");\nconst app = express();\n\napp.get(\"\/hi\", (req, res) => {\n res.send(\"Hi from Express\");\n});\n\napp.listen(3000, () => console.log(\"Server running\"));<\/code><\/pre>\n\n\n\n
\n\n\n\nPart 1: Without Kubernetes<\/h2>\n\n\n\n
If Server 2 crashes, the container dies. Manual intervention is required to provision a new server, install Docker, run the container, and update the load balancer to point to the new IP.<\/p>\n\n\n\n
\n\n\n\nPart 2: Introducing Kubernetes<\/h2>\n\n\n\n
\n\n\n\nPart 3 & 4: Deploying & Request Flow<\/h2>\n\n\n\n
replicas: 2<\/code>, traffic flows from the browser, hits the K8s Service, and is load-balanced to the Pods across Worker Nodes. graph TD B[Browser] –>|GET \/hi| S{Kubernetes Service} S –> P1[Worker 1\\nPod-1] S –> P2[Worker 2\\nPod-2]<\/p>\n\n\n\n
\n\n\n\nPart 5: When a Node Crashes<\/h2>\n\n\n\n
\n\n\n\nPart 6: Scaling<\/h2>\n\n\n\n
replicas: 5<\/code> and the Scheduler spreads pods out: graph TD subgraph Worker 1 P1[Pod-1] P3[Pod-3] P5[Pod-5] end subgraph Worker 2 P2[Pod-2] P4[Pod-4] end<\/p>\n\n\n\n
\n\n\n\nPart 7: Physical vs Logical Relationships<\/h2>\n\n\n\n
\n\n\n\nPart 8: Real-World Analogies<\/h2>\n\n\n\n
\n\n\n\nPart 9: Docker vs Kubernetes<\/h2>\n\n\n\n
Concept<\/th> Docker<\/th> Kubernetes<\/th><\/tr><\/thead> Build Image<\/strong><\/td> docker build<\/code><\/td>Still docker build<\/code> (or similar)<\/td><\/tr>Run App<\/strong><\/td> docker run<\/code><\/td>Deployment<\/strong> (Asks cluster to run Pods)<\/td><\/tr> Smallest Unit<\/strong><\/td> Container<\/td> Pod<\/strong> (Contains the container)<\/td><\/tr> Infrastructure<\/strong><\/td> Docker Host<\/td> Worker Node<\/strong> (Part of a Cluster)<\/td><\/tr> Orchestration<\/strong><\/td> Docker Compose<\/td> Kubernetes<\/strong> (Multi-machine cluster)<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
\n\n\n\nPart 10: Complete Request Lifecycle<\/h2>\n\n\n\n
\n\n\n\nPart 11: Autoscaling (HPA)<\/h2>\n\n\n\n
deployment.yaml<\/code> must define baseline CPU\/Memory requests so Kubernetes knows what “100%” utilization means.<\/li>k8s\/hpa\/hpa.yaml<\/code>), you make autoscaling modular. You can deploy the base app locally without it, and selectively apply the HPA only in Production!<\/p><\/blockquote>\n\n\n\n
\n\n\n\nBonus: Running This Locally<\/h2>\n\n\n\n
minikube start\neval $(minikube docker-env)\ndocker build -t myapp:v1 .<\/code><\/pre>\n\n\n\nkubectl apply -f k8s\/deployment.yaml\nkubectl apply -f k8s\/service.yaml<\/code><\/pre>\n\n\n\n
If you update your app to return the pod name using os.hostname()<\/code>, you can see Kubernetes load balancing in action!<\/p>\n\n\n\ndocker build -t myapp:v2 .\nkubectl set image deployment\/myapp-deployment express-container=myapp:v2<\/code><\/pre>\n\n\n\nTriggering the Autoscaler (Load Testing)<\/h3>\n\n\n\n
kubectl get pods -w<\/code><\/li>kubectl get hpa -w<\/code><\/li>kubectl run -i --tty load-generator --rm --image=busybox:1.28 --restart=Never -- \\\n\/bin\/sh -c \"while sleep 0.01; do wget -q -O- http:\/\/myapp-service\/hi; echo ''; done\"<\/code><\/pre>\n\n\n\n10%<\/code>. Once scaled up, if you stop the load generator, Kubernetes will wait for a 5-minute cooldown period<\/strong> before terminating the extra pods to prevent rapid “flapping”.<\/p><\/blockquote>\n\n\n\nStopping & Deleting the Cluster<\/h3>\n\n\n\n
minikube stop<\/code><\/strong> (Like docker compose stop<\/code>): Safely shuts down the virtual machine, but saves all your data, deployments, and services. You can run minikube start<\/code> tomorrow and pick up exactly where you left off.<\/li>minikube delete<\/code><\/strong> (Like docker compose down -v<\/code>): Completely destroys the cluster and wipes the database. You will get a 100% clean slate the next time you start it, and you will need to run your kubectl apply<\/code> commands again.<\/li><\/ul>\n\n\n\n