Deploy Composio on Kubernetes
Production-ready Helm charts for Composio with comprehensive monitoring, load testing, and enterprise features.
Quick Start
Prerequisites
Ensure you have the following ready:
- Kubernetes cluster (GKE, EKS, AKS, or self-managed)
- Helm 3.x installed
- External PostgreSQL database
- AWS ECR access configured
# Check cluster status
kubectl get nodes
# Verify Helm installation
helm version
Install Knative Components
Install Knative Serving for serverless capabilities:
# Install Knative Serving CRDs
kubectl apply -f https://github.com/knative/serving/releases/download/knative-v1.15.0/serving-crds.yaml
# Install Knative Serving Core
kubectl apply -f https://github.com/knative/serving/releases/download/knative-v1.15.0/serving-core.yaml
# Install Kourier networking layer
kubectl apply -f https://github.com/knative/net-kourier/releases/download/knative-v1.15.0/kourier.yaml
# Configure Kourier as default ingress
kubectl patch configmap/config-network \
--namespace knative-serving \
--type merge \
--patch '{"data":{"ingress-class":"kourier.ingress.networking.knative.dev"}}'
Configure Secrets
Set up your database and API credentials:
# Required environment variables
export POSTGRES_URL="postgresql://<username>:<password>@<host_ip>:5432/<database_name>?sslmode=require"
export REDIS_URL="redis://<username>:<password>@<host>:6379/0" # Optional
export OPENAI_API_KEY="sk-1234567890abcdef..." # Optional
# Run the secret setup script
./secret-setup.sh -r composio -n composio
Deploy with Helm
Install the Composio Helm chart:
# Install the Helm chart
helm install composio ./composio \
--create-namespace \
--namespace composio \
--set namespace.name=composio \
--set externalSecrets.ecr.token="$(aws ecr get-login-password --region us-east-1)" \
--debug
Verify Installation
Check that all services are running:
# Check all pods are running (may take 5-10 minutes)
kubectl get pods -n composio
# Verify Knative services
kubectl get ksvc -n composio
# Check Knative infrastructure
kubectl get pods -n knative-serving
Core Services
Composio's microservices architecture with enterprise-grade reliability
API Layer
Apollo API
v1.0Main Composio API service handling all tool integrations and agent requests
MCP Portal
v1.0Management and Control Portal for monitoring and configuring Composio services
Processing Layer
Thermos
v1.0Workflow engine for orchestrating complex multi-step tool executions
Mercury
v1.0Serverless function service for on-demand tool execution and scaling
Infrastructure Layer
Temporal
v0.64.0Workflow orchestration and state management for reliable task execution
MinIO
v17.11.3Object storage for files, documents, and persistent data management
Redis
v17.11.3In-memory caching layer for improved performance and session management
Resource Requirements
| Configuration | CPU | Memory | Storage | Use Case |
|---|---|---|---|---|
| Minimum | 9 cores | 24GB RAM | 20GB | Development & Testing |
| Recommended | 12+ cores | 32GB RAM | 50GB+ | Production |
| Enterprise | 20+ cores | 64GB+ RAM | 100GB+ | High Load Production |
Service Access
| Service | Description | Port | Type | Access Command | Status |
|---|---|---|---|---|---|
|
Apollo API
|
Main Composio API service | 9900 | NodePort | Running | |
|
MCP Portal
|
Management and Control Portal | 3000 | ClusterIP | Running | |
|
Temporal UI
|
Workflow management interface | 8080 | ClusterIP | Running | |
|
MinIO Console
|
Object storage management | 9001 | ClusterIP | Running |
Troubleshooting
| Issue Category | Common Problems | Quick Fix | Documentation |
|---|---|---|---|
|
Common Issues
|
|
View Docs | |
|
GKE Specific
|
|
View Docs | |
|
Monitoring
|
|
View Docs |
Ready to Deploy?
Get started with Composio on Kubernetes in minutes