docs(vrp): CronJob verified absent on cluster — removal fully complete

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
This commit is contained in:
2026-07-21 07:33:33 +00:00
parent 2f957bb6a6
commit bf99ce2bd1

View File

@@ -18,10 +18,12 @@ full suite green (2018 passed, 2 skipped), whole-branch review clean (no Critica
- The generic freeze-staleness health axis (`_FREEZE_SOURCES = {"opra-pit"}`) stays - The generic freeze-staleness health axis (`_FREEZE_SOURCES = {"opra-pit"}`) stays
- `deribit_funding` (carry edge) untouched - `deribit_funding` (carry edge) untouched
## Outstanding — a DEPLOY action (not code) ## CronJob cluster-resource — VERIFIED not present (no action needed)
The `fxhnt-opra-backfill` CronJob **manifest** is removed from git, but if it exists as a live resource on the Checked 2026-07-21 on `bizworx-prod-kapsule`: `kubectl get cronjob fxhnt-opra-backfill -n foxhunt` → NotFound,
bizworx Kapsule it must be deleted by hand: `kubectl delete cronjob fxhnt-opra-backfill` (ns foxhunt). The git 0 hits cluster-wide. The manifest was never applied live (or already gone), so removing it from git was
removal does not stop a running cluster resource. sufficient. The 5 surviving foxhunt CronJobs (ucits/bybit/ibkr rebalancers, ucits-volume, factory) are all
non-VRP.
## Not-yet-merged ## Merged + pushed
Branch `chore/remove-vrp-code` — awaiting the operator's merge decision. Branch `chore/remove-vrp-code` merged to master (`2f957bb`) and pushed to origin. Live on prod after the next
normal git-sync + rollout-restart.