Deploy Bytebot on Kubernetes with Helm
Helm provides a simple way to deploy Bytebot on Kubernetes clusters.Prerequisites
- Kubernetes cluster (1.19+)
- Helm 3.x installed
- kubectl configured
- 8GB+ available memory in cluster
Quick Start
1
Clone Repository
2
Configure API Keys
Create a
values.yaml
file with at least one API key:3
Install Bytebot
4
Access Bytebot
Basic Configuration
API Keys
Configure at least one AI provider:Resource Limits (Optional)
Adjust resources based on your needs:External Access (Optional)
Enable ingress for domain-based access:Accessing Bytebot
Local Access (Recommended)
External Access
If you configured ingress:- Access at: https://bytebot.your-domain.com
Verifying Deployment
Check that all pods are running:Troubleshooting
Pods Not Starting
Check pod status:- Insufficient memory/CPU: Check node resources with
kubectl top nodes
- Missing API keys: Verify your values.yaml configuration
Connection Issues
Test service connectivity:View Logs
Upgrading
Uninstalling
Advanced Configuration
Using External Secrets
Using External Secrets
If using Kubernetes secret management (Vault, Sealed Secrets, etc.):Create the secret manually:
LiteLLM Proxy Mode
LiteLLM Proxy Mode
For centralized LLM management, use the included LiteLLM proxy:This provides:
- Centralized API key management
- Request routing and load balancing
- Rate limiting and retry logic
Custom Storage
Custom Storage
Configure persistent storage:
Production Security
Production Security
Next Steps
API Reference
Integrate Bytebot with your applications
LiteLLM Integration
Use any LLM provider with Bytebot
Need help? Join our Discord community or check our GitHub discussions.