Production Deployment with Helm & Kubernetes
Deploy Actyze to a Kubernetes cluster using the official Helm chart for production-grade reliability, scaling, and observability.
Prerequisites
- Kubernetes cluster v1.24+ (EKS, GKE, AKS, or self-managed)
- Helm 3.x installed locally
- kubectl configured to access your cluster
- 4 GB+ RAM per node
- A storage class for persistent volumes
- An LLM API key (OpenAI, Anthropic, Azure OpenAI, or Google Gemini)
Steps
1. Add the Actyze Helm repository
helm repo add actyze https://actyze.github.io/helm-charts
helm repo update
2. Create a secrets values file
# Download the template
curl -O https://raw.githubusercontent.com/actyze/helm-charts/main/dashboard/values-secrets.yaml.template
cp values-secrets.yaml.template values-secrets.yaml
Edit values-secrets.yaml with your credentials:
# LLM provider credentials
nexus:
env:
OPENAI_API_KEY: "sk-..."
# or ANTHROPIC_API_KEY, AZURE_OPENAI_API_KEY, etc.
# Database credentials
postgresql:
auth:
postgresPassword: "your-secure-password"
caution
Never commit values-secrets.yaml to version control. Add it to .gitignore.
3. Install Actyze
helm install actyze actyze/dashboard \
-f values-secrets.yaml \
--namespace actyze \
--create-namespace
4. Verify the deployment
kubectl get pods -n actyze
All pods should reach Running status within a few minutes.
5. Access the application
# Port-forward for quick access
kubectl port-forward svc/actyze-frontend 3000:3000 -n actyze
Then open http://localhost:3000. For production, configure an Ingress resource with TLS — see the full Helm chart documentation for examples.
Upgrading
helm repo update
helm upgrade actyze actyze/dashboard \
-f values-secrets.yaml \
--namespace actyze
Full Documentation
The Helm chart supports extensive customisation: Ingress, TLS, resource limits, autoscaling, external databases, and more.
See the helm-charts repository for:
values.yaml— full configuration referenceVALUES_README.md— annotated guide to every settingLLM_PROVIDERS.md— LLM provider setup
Next Steps
- Configure LLM Providers for model selection and fallback chains.
- Monitoring to set up observability for your deployment.
- RBAC to configure role-based access control.