# BF-21081: acb-postgres-credentials SealedSecret

## Status: Already Complete (Verified 2026-06-04)

The `acb-postgres-credentials` SealedSecret already existed in declarative-config at:
`~/declarative-config/k8s/apexalgo-iad/ai-code-battle/acb-postgres-sealedsecret.yml`

Created via commit 2f40563 on 2026-06-03 23:58:08 -0400:
```
feat(apexalgo-iad): add acb-postgres-credentials SealedSecret for ai-code-battle

- Extract credentials from CNPG-created acb-app-credentials-acb-app
- Seal as acb-postgres-credentials with username/password keys
- Required by acb-matchmaker, acb-worker, acb-index-builder

Fixes #bf-21081
```

## Current Verification (2026-06-04 00:15 UTC)

SealedSecret exists and is synced in cluster:
```
NAME                       STATUS   SYNCED   AGE
acb-postgres-credentials            True     ~15m
```

The SealedSecret was successfully unsealed - the `acb-postgres-credentials` secret exists in the `ai-code-battle` namespace with 2 data keys (username, password).

### Pod Status (still Pending due to CPU)
```
acb-index-builder-6669fdbc95-nxwhf   0/1     Pending   0          91m
acb-matchmaker-64f6dc5985-vkbbl      0/1     Pending   0          91m
acb-worker-bf5bfdb98-g9jnn           0/1     Pending   0          91m
acb-worker-bf5bfdb98-mhvn6           0/1     Pending   0          91m
```

Event: `Warning FailedScheduling 0/3 nodes are available: 3 Insufficient cpu.`

## Actual Blocker: Insufficient CPU

The pods are NOT crashing due to missing secrets. They are stuck in **Pending** state due to insufficient CPU:

```
NAME                                 READY   STATUS    RESTARTS   AGE
acb-api-5646489f75-l4zmq             0/1     Pending   0          79m
acb-evolver-7654d8b866-psvk5         0/1     Pending   0          79m
acb-index-builder-6669fdbc95-nxwhf   0/1     Pending   0          91m
acb-matchmaker-64f6dc5985-vkbbl      0/1     Pending   0          91m
acb-worker-bf5bfdb98-g9jnn           0/1     Pending   0          91m
```

Events show: `Warning FailedScheduling 0/3 nodes are available: 3 Insufficient cpu.`

Node capacity (from previous check):
```
NAME                              CPU(cores)
prod-instance-17766512380750059   811m (23%)
prod-instance-17766512418020061   1600m (45%)
prod-instance-17781842321795040   <unknown> (unreachable)
```

## Conclusion

The SealedSecret task was completed prior to this bead assignment. The actual blocker is insufficient CPU resources in the apexalgo-iad cluster.