BookNest could live on Compose 514 for years. It moves to Kubernetes 5,150 for zero-downtime rollouts, health-based traffic, secrets kept out of images and deployments driven from Git 1,932 , all of which carry over unchanged to EKS 24 , GKE 1 or AKS 6 . The same images run, and each Compose idea has a counterpart:
| BookNest in Compose | Kubernetes object | Section |
|---|---|---|
| api and web services | Deployment and its Pods | 6.9 |
| Service names on the network | Service plus a CoreDNS 366,312 name | 6.10 |
| Published port 8080:80 | Ingress or Gateway API route | 6.11 |
| environment: and secrets: | ConfigMap and Secret | 6.12 |
| pgdata named volume | PersistentVolumeClaim, StatefulSet | 6.13, 6.14 |
| Schema created by every replica | One Job or init container | 6.8, 6.15 |
| healthcheck: and resource limits | Probes, requests and limits | 6.16 |
A slow database now fails readiness, so the Pod stops receiving traffic, without failing liveness, so Kubernetes does not restart a healthy API. Images come from Image Registries's registry:3 on localhost:33500, for example localhost:33500/booknest-api:1.3; Local Clusters explains why the cluster is kind 14,561 .