Add PVC for photo uploads to survive pod restarts #73
No reviewers
Labels
No labels
domain:backend
domain:devops
domain:frontend
status:approved
status:in-progress
status:needs-fix
status:qa
type:bug
type:devops
type:feature
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
forgejo_admin/basketball-api!73
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "72-add-photo-upload-pvc"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
Adds a 1Gi PersistentVolumeClaim so player photos at
/data/uploads/photospersist across pod restarts and redeployments. No code changes -- the app already writes to this path.Changes
k8s/pvc.yaml(new) -- 1Gi ReadWriteOnce PVC namedphoto-uploads, uses default storage classk8s/deployment.yaml-- addedphoto-uploadsvolume (from PVC) and volumeMount at/data/uploads/photosk8s/kustomization.yaml-- addedpvc.yamlto resources list (ordered before deployment.yaml so PVC is created first)Test Plan
kubectl get pvc -n basketball-apishowsphoto-uploadsin Bound statePOST /upload/photo, thenkubectl rollout restart deployment basketball-api -n basketball-api, verify photo is still servedReview Checklist
kubectl kustomize k8s/builds cleanlyRelated
plan-2026-03-08-tryout-prepCloses #72