A Deployment manages the lifecycle of a stateless, replicated application. Each replica runs in a Pod containing the application container. section 3.3.3
Deploying an application usually requires a Deployment plus a Service for cluster networking and an Ingress for access from outside the cluster. Manifests define these resources through the Kubernetes API. section 3.3.3 section 3.3.2
A practical Kubernetes inner loop treats a Deployment as part of a repeated workflow:
- Package the application as a container image. section 3.3.2
- Load the image into a local Kubernetes cluster when it is not available through a registry. section 3.3.2
- Define or update the Deployment and related resource manifests. section 3.3.2
- Apply the manifests to create or update the resources. section 3.3.2
Appointments Deployment
An appointments application uses an apps/v1 Deployment named appointments. Its selector and Pod template use the app: appointments label, while the container specifies the application image and obtains PostgreSQL connection values from a Secret.










