jedarden a182fadb0a notes(bf-1bvca): document cluster resource blocking migration verification

- combat_turns migration code is complete and deployed
- Rollout annotation bumped to v4-combat-turns-migration-2026-06-03-b
- apexalgo-iad cluster has insufficient CPU - pods stuck Pending
- Migration will apply once resources are available

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

2026-06-03 23:10:47 -04:00

2.5 KiB

Raw Blame History

bf-1bvca: Deploy combat_turns Column Migration to apexalgo-iad

Summary

Deployed the combat_turns column migration to fix acb-index-builder crashes on apexalgo-iad cluster.

Changes Made

1. Schema Migration (Already Present)

The combat_turns column was already present in ~/declarative-config/k8s/apexalgo-iad/ai-code-battle/acb-schema-init.yml:

Line 46 - In CREATE TABLE statement:

combat_turns  INTEGER NOT NULL DEFAULT 0,

Line 305 - Migration ALTER TABLE statement:

ALTER TABLE matches ADD COLUMN IF NOT EXISTS combat_turns INTEGER NOT NULL DEFAULT 0;

2. Rollout Annotation Bumped

The deployment annotation was bumped to force a restart of the schema-init pod:

checksum/schema: "v4-combat-turns-migration-2026-06-03-b"

3. Commits Already Pushed

All changes were committed and pushed to origin/main:

137b7c5 fix(acb-schema): bump annotation to force combat_turns migration redeploy
51e4a36 fix(schema): bump annotation to force schema-init restart for combat_turns column
f74367f feat(apexalgo-iad): bump schema-init rollout annotation for combat_turns migration
00e1f5c feat(apexalgo-iad): add acb-schema-init deployment with combat_turns migration

Status

✅ Migration SQL is in place (line 305 of acb-schema-init.yml) ✅ Changes committed and pushed to declarative-config ✅ Rollout annotation bumped to v4-combat-turns-migration-2026-06-03-b ✅ ArgoCD has synced the deployment spec (verified via kubectl) ⏸️ BLOCKED: apexalgo-iad cluster has insufficient CPU resources

Cluster Resource Issue

All pods in ai-code-battle namespace are stuck in Pending state:

acb-api-7c46c9d5b6-jfl9w             0/1     Pending   (Insufficient cpu)
acb-evolver-85549b574d-pqbjd         0/1     Pending   (Insufficient cpu)
acb-index-builder-6669fdbc95-nxwhf   0/1     Pending   (Insufficient cpu)
acb-schema-init-74c6894ddb-9g67p     0/1     Pending   (Insufficient cpu)

Error message: 0/3 nodes are available: 3 Insufficient cpu. preemption: 0/3 nodes are available: 3 No preemption victims found for incoming pod.

The schema-init pod cannot schedule to apply the migration. Once cluster resources are available:

New schema-init pod will schedule and apply the migration
Index-builder will no longer crash on "combat_turns does not exist"

Migration Code Complete

The migration code is complete and deployed - only cluster resources are blocking verification.

2.5 KiB Raw Blame History