Fix embedding worker CrashLoopBackOff -- set replicas to 0 #143
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/pal-e-api!143
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "142-fix-embedding-worker-crashloopbackoff-se"
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
Scale the embedding worker deployment to 0 replicas to stop CrashLoopBackOff. The worker depends on Ollama which is currently offline (GPU reclaimed), so the pod restarts indefinitely. Setting replicas to 0 preserves the deployment definition for future re-enablement.
Changes
k8s/embedding-worker.yaml: changedreplicas: 1toreplicas: 0Test Plan
kubectl get pods -n pal-e-docs -l app=pal-e-docs-embedding-workershould show no podskubectl get deploy -n pal-e-docs pal-e-docs-embedding-workerReview Checklist
Related