infra: Add Kubernetes manifests for deployment

[Xhristin3]

Problem Statement

Dockerfiles exist for api, app, and xstreamroll-processing, but no Kubernetes manifests (Deployment, Service, ConfigMap, Secret, Ingress) exist for deploying to a cluster.

Evidence

No k8s/, charts/, deploy/, or infra/ directory exists with Kubernetes resources.

Impact

Cannot deploy to Kubernetes without writing manifests from scratch. No standardized deployment configuration. No health probe configuration for Kubernetes liveness/readiness checks.

Proposed Solution

Create a k8s/ directory with:

1. api-deployment.yaml + api-service.yaml
2. app-deployment.yaml + app-service.yaml
3. processing-deployment.yaml
4. postgres-statefulset.yaml + postgres-service.yaml
5. configmap.yaml (non-secret env vars)
6. secret.yaml template (references to external secret manager)
7. ingress.yaml (routing to api + app)

Acceptance Criteria

• All deployments use the published Docker images
• Health check endpoints used for liveness/readiness probes
• ConfigMaps and Secrets properly separated
• Resource limits and requests defined
• Database credentials not hardcoded

File Map

• k8s/base/*.yaml — new resource files
• k8s/overlays/development/ — dev environment overrides
• k8s/overlays/production/ — production overrides

---

Labels: infrastructure, hackathon
Priority: Medium | Difficulty: Advanced | Estimated Effort: 3d

---

Labels: infrastructure,hackathon
Priority: Medium | Difficulty: Advanced | Estimated Effort: 3d
Backlog ID: REPO-034

[Meet-hybrid]

Can I work on this please?

[OlaGreat]

I'd like to take this on.

I'm a software engineer with experience in blockchain, backend systems, and open-source contribution. I've reviewed the issue and I'm confident I can deliver a clean implementation with tests covering the acceptance criteria. Happy to follow the project's existing conventions.

[MicD746]

hello maintainer please can i work on this issue