Upgrades

This guide covers how to upgrade your self-hosted agent.ceo deployment to newer versions.

Upgrade Process

Agent.ceo follows semantic versioning. Upgrades are performed by updating container images and applying any required migrations.

Step 1: Review the Release Notes

Before upgrading, review the release notes for:

• Breaking changes requiring configuration updates
• Database migration steps
• New required secrets or environment variables
• Minimum Kubernetes version requirements

Step 2: Back Up

Create backups before upgrading:

# Neo4j backup
kubectl exec -n agents-infra neo4j-0 -- neo4j-admin dump --to=/backups/pre-upgrade.dump

# PostgreSQL backup
kubectl exec -n agents-infra postgres-0 -- pg_dump -U agent_ceo > pre-upgrade.sql

Step 3: Update Images

Update the container images in your deployment manifests:

# Update the gateway image
image: ghcr.io/genbrainai/api-gateway:v2.1.0

# Update the agent runtime image
image: ghcr.io/genbrainai/agent-runtime:v2.1.0

Step 4: Apply Migrations

If the release includes database migrations, apply them before restarting:

kubectl apply -f migrations/v2.1.0.yaml

Step 5: Rolling Restart

Perform a rolling restart to apply the new images:

kubectl rollout restart deployment/api-gateway -n agents-gateway
kubectl rollout status deployment/api-gateway -n agents-gateway

Agent pods are updated automatically by the agent manager.

Step 6: Verify

After the upgrade, verify all components are healthy:

# Check pod status
kubectl get pods -n agents
kubectl get pods -n agents-gateway
kubectl get pods -n agents-infra

# Check health endpoints
curl https://agent.yourdomain.com/health

Version Compatibility

Rollback

If an upgrade causes issues, roll back to the previous version:

kubectl rollout undo deployment/api-gateway -n agents-gateway

Restore database backups if migrations were applied.

Next Steps

• Install on Kubernetes — Initial installation
• Networking — Network configuration
• Secrets management — Credential management