notes: document bf-22vc5 retry blocker - iad-ci kubeconfig missing

- Webhook triggers return success but no image published
- Cannot access iad-ci cluster to debug workflow failures
- Requires kubeconfig from Rackspace Spot UI to proceed

notes/bf-22vc5-retry-2026-06-04.md

@@ -0,0 +1,77 @@
+# BF-22VC5: Retry Attempt (2026-06-04)
+
+## Task
+Deploy P0: build acb-enrichment Docker image and re-enable deployment (apexalgo-iad)
+
+## What I Did
+
+### 1. Verified Dockerfile
+- ✅ `cmd/acb-enrichment/Dockerfile` is valid
+- ✅ Uses multi-stage build with golang:1.25-alpine → alpine:3.19
+- ✅ All dependencies included (ca-certificates, tzdata)
+
+### 2. Located Build Infrastructure
+- ✅ WorkflowTemplate: `acb-enrichment-build` in declarative-config
+- ✅ Argo Events sensor triggers on push to master
+- ✅ Deployment manifest: `k8s/apexalgo-iad/ai-code-battle/acb-enrichment-deployment.yml`
+
+### 3. Attempted Build Trigger
+- ✅ Webhook to `https://webhooks-ci.ardenone.com/ai-code-battle` returned "success"
+- ❌ No image appeared on Docker Hub after 30 seconds
+- ❌ Forgejo registry returns "no available server"
+
+### 4. Checked Infrastructure Access
+| Access Method | Status | Result |
+|---------------|--------|--------|
+| `~/.kube/iad-ci.kubeconfig` | ❌ Missing | Cannot access iad-ci cluster |
+| kubectl-proxy-iad-ci | ❌ No DNS record | No proxy access |
+| ArgoCD on rs-manager | ❌ Empty response | Cannot check cluster status |
+| Docker Hub: ronaldraygun/acb-enrichment | ❌ 0 tags | No images built |
+| Forgejo registry | ❌ "no available server" | Registry not accessible |
+
+## Blocker Analysis
+
+The webhook succeeds, but images are not being published. This indicates:
+1. The Argo Events sensor is triggering the workflow
+2. The workflow starts but fails at the push step
+3. Most likely cause: missing `docker-hub-registry` secret in iad-ci
+
+## Why This Is Blocked
+
+Without access to the iad-ci cluster (`~/.kube/iad-ci.kubeconfig`), I cannot:
+1. Check workflow status: `kubectl get workflows -n argo-workflows`
+2. View workflow logs to confirm failure point
+3. Verify `docker-hub-registry` secret exists
+4. Manually trigger a debug workflow
+5. Check pod status for the build job
+
+## Required to Unblock
+
+1. **Obtain iad-ci kubeconfig** from Rackspace Spot UI
+   - Save to `/home/coding/.kube/iad-ci.kubeconfig`
+   - This provides cluster-admin access to iad-ci cluster
+
+2. **Once kubeconfig is available:**
+   ```bash
+   # Check recent workflows
+   kubectl --kubeconfig=/home/coding/.kube/iad-ci.kubeconfig \
+     get workflows -n argo-workflows | grep acb-enrichment
+
+   # Verify secret exists
+   kubectl --kubeconfig=/home/coding/.kube/iad-ci.kubeconfig \
+     get secret docker-hub-registry -n argo-workflows
+
+   # If missing, create secret from Docker Hub credentials
+   kubectl --kubeconfig=/home/coding/.kube/iad-ci.kubeconfig \
+     create secret docker-registry docker-hub-registry \
+     --docker-server=registry-1.docker.io \
+     --docker-username=<username> \
+     --docker-password=<password> \
+     -n argo-workflows
+   ```
+
+## Status
+**BLOCKED** - Requires iad-ci kubeconfig to proceed
+
+## Time
+2026-06-04 06:55 UTC