Skip to content

15.2 Kubernetes Manifests

Sprint: Sprint 15 - Deployment
Feature ID: 15.2
Subtasks: 15.2.1, 15.2.2, 15.2.3

Objective

Deliver "Kubernetes Manifests" within Sprint 15 - Deployment.

Dependencies

Aggregated from the subtasks below (prerequisite task IDs and enablers):

  • 15.1.1
  • 15.2.1

Subtasks

15.2.1 Base manifests/Helm charts per service

  • ID: 15.2.1
  • Title: Author Kubernetes Deployment/Service/Ingress per service
  • Description: Helm charts (or Kustomize bases) for every service: Deployment (probes, resource requests/limits), Service, and Ingress/Gateway route for externally exposed paths. Stateless, HPA-ready (NFR-03).
  • Business Purpose: Declarative, scalable deployment (NFR-03, ADR-014).
  • Inputs: analysis Section 7.2, NFR-03, ADR-010.
  • Outputs: Helm charts/manifests per service.
  • Acceptance Criteria:
  • Each service deploys to a local cluster (Minikube/Kind); liveness/readiness probes pass; the gateway is reachable via Ingress.
  • Dependencies: 15.1.1
  • Complexity: L

15.2.2 ConfigMaps and Secrets

  • ID: 15.2.2
  • Title: Externalize config via ConfigMaps and Secrets
  • Description: Move per-service configuration to ConfigMaps and sensitive values (DB creds, JWT signing key, PII encryption key) to Secrets, replacing config-server for prod (ADR-010). PII/JWT keys are mounted from Secrets (NFR-06).
  • Business Purpose: Production configuration and secret management (ADR-010, NFR-06).
  • Inputs: ADR-010, NFR-06, 4.1.x.
  • Outputs: ConfigMap/Secret manifests + key wiring.
  • Acceptance Criteria:
  • Services read config from ConfigMaps and secrets from Secrets in-cluster; no plaintext secret is committed.
  • Dependencies: 15.2.1
  • Complexity: M

15.2.3 Stateful dependencies in-cluster

  • ID: 15.2.3
  • Title: Provision Postgres, Kafka, Redis, Schema Registry, observability in-cluster
  • Description: Provide manifests/Helm values (or documented managed-service hooks) for the stateful dependencies the services need, mirroring the local compose stack (ADR-006, ADR-009, ADR-012).
  • Business Purpose: A complete runnable cluster environment.
  • Inputs: analysis Section 7.1, Sprint 01 infra.
  • Outputs: Dependency manifests/Helm values.
  • Acceptance Criteria:
  • The dependency stack runs in-cluster and services connect to it; the observability stack receives traces/logs/metrics.
  • Dependencies: 15.2.1
  • Complexity: L

Acceptance Criteria

Each subtask above carries its own objective, testable acceptance criteria. This feature is complete when every subtask's acceptance criteria are met.

Deliverables

  • Helm charts/manifests per service.
  • ConfigMap/Secret manifests + key wiring.
  • Dependency manifests/Helm values.

Definition of Done

  • All subtasks (15.2.1, 15.2.2, 15.2.3) completed and their acceptance criteria verified.
  • All listed dependencies satisfied.
  • Build and tests green per the global conventions in ../README.md (Section 3).