Deploy Helicone using Kubernetes and Helm. Quick setup guide for running a containerized instance of the LLM observability platform on your Kubernetes cluster.
The Helm chart deploys the complete Helicone stack on Kubernetes. Terraform creates AWS S3, Aurora, and EKS resources to run the Helicone project on. The Helm chart is available in the Helicone Helm repository. Previous version: v2
charts/
and
customize as needed for your configuration.terraform init
, followed by terrform validate
followed by
terraform apply
You can now deploy all Helicone components with a single command using the provided
helm-compose.yaml
configuration:
This will deploy the complete Helicone stack including:
To tear down all components:
Alternatively, you can install components individually:
Install necessary helm dependencies:
Use values.example.yaml
as a starting point, and copy into values.yaml
Copy secrets.example.yaml
into secrets.yaml
, and change the secrets according to your setup.
Install/upgrade each Helm chart individually:
Verify the deployment:
ArgoCD is deployed as part of the helicone-argocd component and provides GitOps capabilities for continuous deployment. It monitors your Git repositories and automatically synchronizes your Kubernetes cluster state with the desired state defined in your Git repos.
Port-forward to access the ArgoCD server:
Access the ArgoCD UI at: https://localhost:8080
Get the initial admin password:
Login with username admin
and the password retrieved above.
Grafana is deployed as part of the helicone-monitoring component and provides observability dashboards for monitoring your Helicone deployment. It works alongside Prometheus to collect and visualize metrics from all your services.
Port-forward to access the Grafana server:
Access the Grafana UI at: http://localhost:3000
Get the admin password (if using default configuration):
Login with username admin
and the password retrieved above.
Pre-configured dashboards for Helicone services should be available under the Dashboards section.
Go to terraform/s3, then terraform validate
followed by terraform apply
If minio is enabled, then it will take the place of S3. Minio is a storage solution similar to AWS S3, which can be used for local testing. If minio is disabled by setting the enabled flag under that service to false, then the following parameters are used to configure the bucket:
Make sure to enable the following CORS policy on the S3 bucket, such that the web service can fetch URL’s from the bucket. To do so in AWS, in the bucket settings, set the following under Permissions -> Cross-origin resource sharing (CORS):
To set up an Aurora postgresql database using Terraform, follow these steps:
Navigate to the terraform/aurora directory:
Initialize Terraform:
Validate the Terraform configuration:
Apply the Terraform configuration to create the Aurora cluster:
After the aurora resource is created, make sure to set enabled to false for postgresql. This will allow the aurora cluster to be used in its place.
Deploy Helicone using Kubernetes and Helm. Quick setup guide for running a containerized instance of the LLM observability platform on your Kubernetes cluster.
The Helm chart deploys the complete Helicone stack on Kubernetes. Terraform creates AWS S3, Aurora, and EKS resources to run the Helicone project on. The Helm chart is available in the Helicone Helm repository. Previous version: v2
charts/
and
customize as needed for your configuration.terraform init
, followed by terrform validate
followed by
terraform apply
You can now deploy all Helicone components with a single command using the provided
helm-compose.yaml
configuration:
This will deploy the complete Helicone stack including:
To tear down all components:
Alternatively, you can install components individually:
Install necessary helm dependencies:
Use values.example.yaml
as a starting point, and copy into values.yaml
Copy secrets.example.yaml
into secrets.yaml
, and change the secrets according to your setup.
Install/upgrade each Helm chart individually:
Verify the deployment:
ArgoCD is deployed as part of the helicone-argocd component and provides GitOps capabilities for continuous deployment. It monitors your Git repositories and automatically synchronizes your Kubernetes cluster state with the desired state defined in your Git repos.
Port-forward to access the ArgoCD server:
Access the ArgoCD UI at: https://localhost:8080
Get the initial admin password:
Login with username admin
and the password retrieved above.
Grafana is deployed as part of the helicone-monitoring component and provides observability dashboards for monitoring your Helicone deployment. It works alongside Prometheus to collect and visualize metrics from all your services.
Port-forward to access the Grafana server:
Access the Grafana UI at: http://localhost:3000
Get the admin password (if using default configuration):
Login with username admin
and the password retrieved above.
Pre-configured dashboards for Helicone services should be available under the Dashboards section.
Go to terraform/s3, then terraform validate
followed by terraform apply
If minio is enabled, then it will take the place of S3. Minio is a storage solution similar to AWS S3, which can be used for local testing. If minio is disabled by setting the enabled flag under that service to false, then the following parameters are used to configure the bucket:
Make sure to enable the following CORS policy on the S3 bucket, such that the web service can fetch URL’s from the bucket. To do so in AWS, in the bucket settings, set the following under Permissions -> Cross-origin resource sharing (CORS):
To set up an Aurora postgresql database using Terraform, follow these steps:
Navigate to the terraform/aurora directory:
Initialize Terraform:
Validate the Terraform configuration:
Apply the Terraform configuration to create the Aurora cluster:
After the aurora resource is created, make sure to set enabled to false for postgresql. This will allow the aurora cluster to be used in its place.