Essential session storage is required to sign in. Optional analytics remain off unless you allow them.
Deploy a small app plus a stateful backing service (e.g. a database) on Kubernetes: a Deployment for the stateless app and a StatefulSet (or a Deployment + PVC) for the stateful part with persistent storage, a Service for each, configuration via a ConfigMap and a Secret (mounted/injected, not baked into the image), liveness and readiness probes, and HTTP routing in via an Ingress. Data must survive a pod restart.
Right controller per component (Deployment vs StatefulSet); a PVC/PV gives persistence that survives pod restart.
ConfigMap + Secret supply config at runtime (env/volume); nothing sensitive baked into the image.
Services connect components by label; an Ingress (with a controller) routes external traffic correctly.
Liveness and readiness probes are set and meaningfully different; rollout waits for readiness.
Use this README structure to make the work reviewable.
DevPath fetches a read-only, size-capped snapshot. Submitted code is never executed.
# A multi-component app with config, storage & ingress ## Goal Deploy a small app plus a stateful backing service (e.g. a database) on Kubernetes: a Deployment for the stateless app and a StatefulSet (or a Deployment + PVC) for the stateful part with persistent storage, a Service for each, configuration via a ConfigMap and a Secret (mounted/injected, not baked into the image), liveness and readiness probes, and HTTP routing in via an Ingress. Data must survive a pod restart. ## Acceptance criteria - [ ] Workloads & storage: Right controller per component (Deployment vs StatefulSet); a PVC/PV gives persistence that survives pod restart. - [ ] Config & secrets: ConfigMap + Secret supply config at runtime (env/volume); nothing sensitive baked into the image. - [ ] Networking: Services connect components by label; an Ingress (with a controller) routes external traffic correctly. - [ ] Health: Liveness and readiness probes are set and meaningfully different; rollout waits for readiness. ## 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.