Description
🤖 Generated by the Agentic Engineer
Description
The node-local backup agent can remain unschedulable when a worker's memory requests are full. Its default scheduling priority cannot make room, although movable lower-priority workloads are present. A monitoring reservation refresh has already landed, so repeating that earlier repair does not resolve this newly observed agent admission failure.
Steps to Reproduce
- Render the pinned Velero chart with the production values.
- Observe that the node-agent has no declared priority tier.
- Restart an agent on a worker with insufficient unreserved memory and observe it remain pending.
Expected Behavior
The node-local backup agent must have schedulable capacity without lowering its memory request or displacing databases, storage clients, or critical infrastructure.
Actual Behavior
A current read-only observation shows an unschedulable backup agent. The server is available, but that does not establish complete node-local backup coverage.
Acceptance Criteria
- Reproduce the missing scheduling tier with the actual pinned chart before changing configuration.
- Reuse the existing modest storage priority tier for the production node-agent only; retain equal database priority and higher critical-infrastructure priority.
- Preserve the single server, resource requests, backup inclusion, credentials, volumes, transfer settings, and bounded rolling update.
- Pass regression controls, exact-head review and CI, then deliver through the normal protected merge queue after fix: unblock safe recovery of interrupted storage maintenance #4775.
- Read back agent readiness and unchanged database redundancy; prove a subsequent full backup before declaring the broader backup incident recovered.
Part of #4723. This does not claim to fix the separately tracked source-pinned transfer admission behavior or close #4729's full-backup proof.
Incident/WIP exception: this is confirmed live backup-agent breakage, not proactive intake. The narrow repair is expedited while the already-reviewed maintenance recovery is validating in the queue. Private node identities, resource telemetry, and raw logs remain outside this issue.
Metadata
Metadata
Assignees
Labels
Type
Fields
Priority
Effort
Projects
- StatusShow more project fields✅ Done
Activity
chore: agent-claim #4781 nonce=9d455c877cd0043144c2be6e3716aef4