feat: archive build/deploy logs to MinIO for post-eviction retrieval

[vigneshrajsb]

Problem

Build and deploy job logs are permanently lost once k8s Job pods are evicted or TTL-expired (~24h):

• Job history is fetched entirely from live k8s (getNativeBuildJobs, getDeploymentJobs)
• Logs are streamed from live pods via WebSocket
• When pods disappear the UI renders a broken NotFound state with no recovery path

Solution

Add MinIO as an optional in-cluster S3-compatible object store. Logs are archived at job completion time and served back transparently — the UI sees a new Archived status instead of NotFound.

Architecture

Job completes → archive logs.txt + metadata.json to MinIO
                 └── {namespace}/{jobType}/{serviceName}/{jobName}/

Pod evicted after TTL...

UI requests log stream info → backend returns status='Archived' + archivedLogs text
UI requests job list       → archived jobs merged into live k8s results (deduplicated by jobName)

Changes

New files

File	Purpose
src/server/lib/objectStore/s3Client.ts	MinIO client singleton (env-configured)
src/server/services/logArchival.ts	LogArchivalService: archiveLogs, getArchivedLogs, listArchivedJobs, ensureBucket, configureRetention
src/server/services/types/logArchival.ts	ArchivedJobMetadata interface

Modified files

File	Change
src/shared/config.ts	Export MINIO_* env vars with safe defaults
next.config.js	Add MinIO vars to serverRuntimeConfig
src/server/services/types/globalConfig.ts	Add logArchival?: { enabled, retentionDays }
src/server/services/types/logStreaming.ts	Add 'Archived' status; add archivedLogs? field
src/server/lib/nativeBuild/engines.ts	Archive build logs after job completes (success + failure paths)
src/server/lib/nativeHelm/helm.ts	Archive deploy logs after job completes
src/server/lib/kubernetes/getNativeBuildJobs.ts	Merge archived build jobs; add source field to BuildJobInfo
src/server/lib/kubernetes/getDeploymentJobs.ts	Merge archived deploy jobs; add source field to DeploymentJobInfo
src/server/services/logStreaming.ts	Fall back to archived log lookup when k8s returns NotFound
helm/web-app/Chart.yaml	Add MinIO subchart dependency (disabled by default)
helm/environments/local/lifecycle.yaml	Add minio: config section

Key design decisions

Feature-gated: all MinIO calls check globalConfig.logArchival?.enabled. Enabling the infra (MinIO pod) is safe — nothing archives until the flag is set in DB.

Non-blocking: archival failures are caught and logged as warnings — they never fail the build/deploy flow.

Deduplication: merged archived jobs are deduplicated by jobName against live k8s results, so a completing job never appears twice.

Enabling

1. Deploy MinIO via the companion helm-charts PR
2. Insert into global_config:

{ "logArchival": { "enabled": true, "retentionDays": 14 } }

Related PRs

• helm-charts: feat: add MinIO subchart for build/deploy log archival (v0.7.0) helm-charts#32 — MinIO subchart
• lifecycle-ui: https://github.com/GoodRxOSS/lifecycle-ui/pull/28 — UI archived log rendering

Test plan

• pnpm lint passes ✅
• pnpm ts-check — no new errors (3 pre-existing in engines.ts) ✅
• pnpm test — 951/951 pass ✅
• With logArchival.enabled=false (default): system behavior identical to before, no MinIO calls
• With logArchival.enabled=true: trigger a build, verify logs.txt + metadata.json appear in MinIO bucket
• Delete the job pod manually, verify it still appears in the build job list with source='archived'
• Click the archived job in the UI — logs render via staticContent (not WebSocket)

🤖 Generated with Claude Code