Production Deployment Guide
This guide provides detailed instructions for deploying AgentArea using Docker and Kubernetes. For infrastructure overview and monitoring setup, see the Infrastructure and Monitoring sections.
π― Deployment Strategies
Docker Compose
Best for: Small to medium deployments, single-server setups
- Quick setup and deployment
- Integrated service orchestration
- Built-in networking and volumes
- Perfect for staging environments
Kubernetes
Best for: Enterprise deployments, high availability
- Auto-scaling and load balancing
- Rolling updates and rollbacks
- Service discovery and networking
- Production-grade orchestration
π³ Docker Compose Deployment
Prerequisites
- Docker Engine 20.0+
- Docker Compose 2.0+
- 4GB+ RAM, 20GB+ storage
- Valid domain name with SSL certificate
Production Docker Compose
- docker-compose.prod.yml
- .env.production
Deployment Steps
1
Server Preparation
2
Configure Environment
3
Deploy Services
4
Configure SSL & DNS
βΈοΈ Kubernetes Deployment
Prerequisites
- Kubernetes cluster 1.24+
- kubectl configured
- Helm 3.0+
- Persistent volume provisioner
- Ingress controller
Helm Chart Deployment
- values.yaml
- Deployment Commands
Kubernetes Security Configuration
βοΈ Cloud Platform Deployment
AWS ECS with Fargate
- Task Definition
- Terraform Configuration
Google Cloud Run
π Monitoring & Observability
Prometheus & Grafana
- Prometheus Configuration
- Grafana Dashboard
Alerting Rules
π CI/CD Pipeline
GitHub Actions
π§ Maintenance & Operations
Database Maintenance
Scaling Considerations
Horizontal Scaling
- Add more API server replicas
- Use load balancer for distribution
- Implement sticky sessions if needed
- Scale database read replicas
Vertical Scaling
- Increase CPU and memory limits
- Optimize database configuration
- Tune connection pools
- Monitor resource utilization
For production deployments, always follow security best practices, implement proper monitoring, and have a disaster recovery plan in place. Consider consulting with our enterprise team for large-scale deployments.
CI/CD container publishing
Our GitHub Actions build and push all Docker images in the monorepo.- On pushes to
main, all images are published to Docker Hub with tags:devcommit-<short-sha>
- Release workflow (
Release Images) builds all images and tags them with:- the provided release version (for example,
v1.2.3) latest
- the provided release version (for example,
- Helm charts in
charts/*/Chart.yamlare automatically bumped to the release version via the release workflow and a PR is opened.
agentarea/agentarea-<component> on Docker Hub for components:
agentarea-api, agentarea-worker, agentarea-frontend, agentarea-operator, agentarea-mcp-manager.
Authentication for publishing uses repository secrets:
DOCKERHUB_USERNAMEDOCKERHUB_PASSWORD