Remote Developer - Claude Code instances in isolated Kubernetes pods
ee1c214b7e
All checks were successful
ci/woodpecker/push/woodpecker Pipeline was successful
Three bugs in the notify provisioner DNS record upsert:
1. rec.Record ("DKIM"/"SPF") was used as the DNS record type — Cloudflare
doesn't know those labels. Fix: use rec.DNSType ("TXT"/"MX") from the
resendDNSRecord.type JSON field, which is the actual DNS record type.
2. rec.Name from Resend is already relative to the zone apex
(e.g., "resend._domainkey.mail.project-name"), not relative to the
registered domain. Code was doing rec.Name + "." + host which produced
a doubled subdomain. Fix: pass rec.Name directly — Cloudflare's
normalizeName appends ".baseDomain" to build the correct FQDN.
3. MX records have priority 10 in Resend's response but DNSRecord had no
Priority field and Cloudflare CreateRecord/UpdateRecord didn't send it.
Fix: add Priority int to domain.DNSRecord and include it in the body
for both Create and Update when non-zero.
These bugs caused DKIM/SPF DNS records to never be created for any project.
Re-provision affected projects using POST /projects/{id}/notify/provision
after clearing NOTIFY_RESEND_DOMAIN_ID from the credential store.
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
|
||
|---|---|---|
| .claude/guides | ||
| ai-lookup | ||
| changelog | ||
| cmd | ||
| cookbooks | ||
| deployments/k8s/base | ||
| docs | ||
| examples | ||
| history | ||
| ideas/aeres | ||
| internal | ||
| pkg/api | ||
| scripts | ||
| sdk | ||
| tests/e2e | ||
| .env.local.example | ||
| .gitignore | ||
| .gitkeep-ci | ||
| .golangci.yml | ||
| .woodpecker.yml | ||
| aeries-preparation-thoughts.md | ||
| app-vision-gaps.md | ||
| app-vision-roadmap.md | ||
| app-vision.md | ||
| CHANGELOG.md | ||
| CLAUDE.md | ||
| CODING_GUIDELINES.md | ||
| docker-compose.yaml | ||
| Dockerfile | ||
| Dockerfile.api | ||
| Dockerfile.api.prebuild | ||
| Dockerfile.worker | ||
| go.mod | ||
| go.sum | ||
| IMPLEMENTATION_PLAN_V2.md | ||
| IMPLEMENTATION_PLAN.md | ||
| Makefile | ||
| PLAN.md | ||
| QUICKSTART.md | ||
| README.md | ||
| vision.md | ||
rdev - Remote Developer
Run Claude Code in isolated Kubernetes pods on your k3s cluster.
Quick Start
# 1. Set kubeconfig (REQUIRED - this is k3s, not GKE)
export KUBECONFIG=~/.kube/orchard9-k3sf.yaml
# 2. Authenticate Claude locally (if not already)
claude
# 3. Create credentials secret
./scripts/create-credentials-secret.sh
# 4. Deploy
./scripts/deploy.sh
# 5. Verify
./scripts/verify.sh
Usage
# Check Claude version
kubectl exec -n rdev claudebox-0 -- claude --version
# Interactive Claude session
kubectl exec -it -n rdev claudebox-0 -- claude "what can you help me with?"
# Run in workspace
kubectl exec -it -n rdev claudebox-0 -- bash
cd /workspace
claude "create a hello world go program"
Architecture
k3s cluster
└── rdev namespace
└── claudebox-0 (StatefulSet)
├── Claude Code CLI
├── /workspace (20Gi PVC via Longhorn)
└── /root/.claude (credentials from secret)
Roadmap
- v0.1: Base case - single claudebox pod
- v0.2: Real workspace mounting (pantheon, aeries)
- v0.3: Git integration (push/pull)
- v0.4: Discord bot control
- v0.5: Streaming output
- v0.6: Multi-project routing
Development
# Build image locally
docker build -t rdev-claudebox:dev .
# Build and push to Artifact Registry
./scripts/build-push.sh v0.1.0
Troubleshooting
# Check pod status
kubectl get pods -n rdev
# View pod logs
kubectl logs claudebox-0 -n rdev
# Describe pod for events
kubectl describe pod claudebox-0 -n rdev
# Check credentials mount
kubectl exec -n rdev claudebox-0 -- ls -la /root/.claude/