kubeclaw/config
sscoble d7d05ff316 feat: wire demo concierge to Discord for end-to-end onboarding testing (#3)
## Summary

Wires the demo concierge agent (kubeclaw-agent-demo-concierge in cust-demo) to Discord for end-to-end onboarding testing.

## Changes

### Config files added
- **02-channel-discord-demo.yaml** — Channel CR for Discord (discord-demo)
- **06-agent-demo-concierge.yaml** — Agent CR sample with Discord env vars
- **agent-pod-demo-concierge.yaml** — Working pod manifest with `DISCORD_BOT_TOKEN` from secret and `GATEWAY_ALLOW_ALL_USERS=true`

### Applied to cluster
- Secret `channel-tokens` created in `cust-demo` (with placeholder token)
- Channel `discord-demo` CR applied
- Pod recreated — now picks up `DISCORD_BOT_TOKEN` env var

## Known Issue: Missing discord.py in container image

The Hermes Discord adapter (`gateway/platforms/discord.py`) exists in the image but fails at runtime because `discord.py` is not installed. The `hermes-speckl/sme:latest` image needs `discord.py` added to its Python dependencies.

## Verification

```
kubectl logs -n cust-demo kubeclaw-agent-demo-concierge --tail=5
WARNING gateway.run: Discord: discord.py not installed
WARNING gateway.run: No adapter available for discord
```

The old "No messaging platforms enabled" warning is gone.

## What is needed next
1. Rebuild image with discord.py
2. Replace placeholder token in channel-tokens Secret
3. Fix agent_controller.go buildEnv() to pass through spec.env vars

Closes #2

Co-authored-by: Marcus (agent-cos) <cos@marcus.local>
Reviewed-on: https://os.scoble.me/forgejo/forgejo/sscoble/kubeclaw/pulls/3
2026-05-14 21:12:10 -07:00
..
crd/bases feat: full kubeclaw operator — CRDs, controllers, deploy manifests, Helm chart 2026-05-12 17:08:31 -07:00
deploy feat: full kubeclaw operator — CRDs, controllers, deploy manifests, Helm chart 2026-05-12 17:08:31 -07:00
rbac feat: full kubeclaw operator — CRDs, controllers, deploy manifests, Helm chart 2026-05-12 17:08:31 -07:00
samples feat: wire demo concierge to Discord for end-to-end onboarding testing (#3) 2026-05-14 21:12:10 -07:00