You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Remove temporary operator placement before host maintenance #6432
Track removal and expiry of the short-lived operator placement prepared in #6427. It is disabled by default and requires a separate reviewed activation.
Entry condition: runtime adoption and the required backup readbacks are verified. Those intermediate receipts are sufficient; waiting for the entire migration issue to close would create a dependency cycle.
Expiry: remove the optional placement before the first eligible host maintenance following those checks. Record the cleanup in Git and remove the obsolete component and test hooks when their temporary purpose is complete.
Acceptance:
Ordinary operator placement is restored through a reviewed change with resource and availability safeguards preserved.
Fresh fallback request/allocation and resident-memory budgets qualify; the current operator rollout is Ready and available and reconciliation remains healthy.
Cleanup and readback finish before any affected host is cordoned, rebuilt or retired.
The cleanup entry condition is currently held by #6442, which owns verified adoption of the required runtime tooling. Added that native dependency so the existing blocked state identifies its actual prerequisite. #6433 remains open for recovery acceptance.
Resume this cleanup after the runtime-adoption receipt and required backup readbacks qualify; the entire #5582 migration need not close first. Keep the original expiry: remove any activated temporary placement through reviewed Git delivery and verify ordinary placement before the first affected host maintenance. This record authorizes no activation or host operation.
Activity
chore: agent-claim #6432 nonce=418c382defa1531a7f825fc3228ef17d
chore: agent-claim #6432 nonce=98511fc0ac63beb080e9a2aef54d21db
devantler commentedon Nov 16, 2026
The cleanup entry condition is currently held by #6442, which owns verified adoption of the required runtime tooling. Added that native dependency so the existing blocked state identifies its actual prerequisite. #6433 remains open for recovery acceptance.
Resume this cleanup after the runtime-adoption receipt and required backup readbacks qualify; the entire #5582 migration need not close first. Keep the original expiry: remove any activated temporary placement through reviewed Git delivery and verify ordinary placement before the first affected host maintenance. This record authorizes no activation or host operation.
chore: agent-claim #6432 nonce=f0d21a99379ecf1f0e72d5efc8b7e384