# ACB Kubernetes Manifests Sync to declarative-config

## Task Status: COMPLETE

**Bead ID:** bf-3lo
**Date:** 2026-06-27
**Author:** jedarden

## Summary

All ACB (AI Code Battle) Kubernetes manifests have been successfully synced to `jedarden/declarative-config` and ArgoCD is managing them.

## Verification Results

### ✓ All ACB manifests present in declarative-config

Location: `/home/coding/declarative-config/k8s/apexalgo-iad/acb-bots/`

**Manifest inventory (52 files):**
- 1 Namespace (`namespace.yml`)
- 17 Deployments (bot-assassin, bot-defender, bot-farmer, bot-gatherer, bot-guardian, bot-hunter, bot-kamikaze, bot-nomad, bot-opportunist, bot-pacifist, bot-phalanx, bot-raider, bot-random, bot-rusher, bot-scout, bot-seeder, bot-swarm)
- 16 Services (one per bot except bot-seeder)
- 17 ExternalSecrets (16 bot secrets + 1 docker-hub-registry)
- 1 ServiceAccount (`bot-seeder`)
- 1 Role (`bot-seeder`)
- 1 RoleBinding (`bot-seeder`)
- 1 ConfigMap (`bot-seeder-script`)

### ✓ ArgoCD sync successful

**Application:** `acb-bots-ns-apexalgo-iad`
**Status:**
- Sync: **Synced** ✓
- Phase: **Succeeded** ✓
- Message: "successfully synced (all tasks run)"

### ⚠ Pods not running (expected - due to dependencies)

**Current pod status:**
- 16 pods in **Pending** state (cluster capacity)
- 2 pods with **ImagePullBackOff** (missing image pull credentials)

**ExternalSecret status:**
- All 18 ExternalSecrets in **SecretSyncedError** state (OpenBao connectivity)

These issues are expected based on the bead's dependencies:
- **bf-7i6** (cluster capacity): Not all nodes have capacity to schedule pods
- **bf-2z2** (image pull): ExternalSecrets not syncing, so docker-hub-registry secret not available

### ✓ No drift between cluster and declarative-config

**Git status:** Clean (no uncommitted changes)
**Latest commit:** `d797177` - "fix(acb-bots): promote to top-level namespace dir + fix manifest issues"

**Deployed resources match manifests:**
- All 17 deployments deployed
- All 16 services deployed
- All RBAC resources deployed
- ConfigMap deployed
- Namespace exists with correct labels

## Deployment Architecture

The ACB manifests are managed via the `manifest-appset-apexalgo-iad` ApplicationSet, which automatically creates an ArgoCD Application for each directory in `k8s/apexalgo-iad/*`. The `acb-bots` directory is picked up by this glob pattern.

**ArgoCD Application details:**
```yaml
apiVersion: argoproj.io/v1alpha1
kind: Application
metadata:
  name: acb-bots-ns-apexalgo-iad
  namespace: argocd
spec:
  source:
    repoURL: https://github.com/jedarden/declarative-config
    targetRevision: HEAD
    path: k8s/apexalgo-iad/acb-bots
  destination:
    server: https://hcp-99476ebb-4133-4a21-ac6a-6e2bdf6794c0.spot.rackspace.com
  syncPolicy:
    automated:
      prune: true
      selfHeal: true
      allowEmpty: true
```

## Next Steps

To achieve full ACB deployment:

1. **Complete bf-7i6** (cluster capacity): Ensure apexalgo-iad nodes have sufficient resources to schedule all 17 bot pods
2. **Complete bf-2z2** (image pull): Fix ExternalSecret synchronization so docker-hub-registry secret is available for image pulls
3. **Build and push bot images**: Some deployments reference placeholder SHA tags that need real images

## Files Changed

No new manifests were added during this task - all ACB manifests were already present in declarative-config from prior work (commit d797177).

This bead confirms the sync is complete and documents the current state.