Essential session storage is required to sign in. Optional analytics remain off unless you allow them.
On a local cluster (minikube, kind, or k3d), deploy a containerized app with a Deployment manifest (replicas, a pod template, labels) and expose it with a Service. Then prove orchestration: scale the replicas up and down with kubectl, delete a pod and watch a replacement appear, and reach the app through the Service (not a pod IP). Everything declarative via `kubectl apply -f`.
Valid Deployment + Service manifests; selector labels match; the app is reachable via the Service.
Deleting a pod yields a replacement; scaling replicas works; demonstrates pods are ephemeral (new IPs).
Changes made via apply -f manifests in version control, not ad-hoc imperative edits.
Can explain why clients use the Service, not a pod IP, and what the Deployment controller is doing.
Use this README structure to make the work reviewable.
DevPath fetches a read-only, size-capped snapshot. Submitted code is never executed.
# Deploy, expose and self-heal an app on Kubernetes ## Goal On a local cluster (minikube, kind, or k3d), deploy a containerized app with a Deployment manifest (replicas, a pod template, labels) and expose it with a Service. Then prove orchestration: scale the replicas up and down with kubectl, delete a pod and watch a replacement appear, and reach the app through the Service (not a pod IP). Everything declarative via `kubectl apply -f`. ## Acceptance criteria - [ ] Deployment & Service: Valid Deployment + Service manifests; selector labels match; the app is reachable via the Service. - [ ] Self-healing & scaling: Deleting a pod yields a replacement; scaling replicas works; demonstrates pods are ephemeral (new IPs). - [ ] Declarative workflow: Changes made via apply -f manifests in version control, not ad-hoc imperative edits. - [ ] Understanding: Can explain why clients use the Service, not a pod IP, and what the Deployment controller is doing. ## Verification - [ ] Document installation and run commands. - [ ] Record automated checks and their exact commands. - [ ] Add representative output, screenshots, or a short demo where useful. - [ ] Confirm failure paths and known constraints. ## Decision log ### Decision title - Context: - Choice: - Alternatives considered: - Tradeoffs: ## Evidence - Link each rubric criterion to the file, test, or artifact that demonstrates it. ## Known limitations - List what is intentionally out of scope and what should be improved next.