The lightrun Helm chart provides a reliable and efficient way to deploy and manage Lightrun on Kubernetes. It includes all the essential components for a smooth setup and can scale seamlessly to support large deployments.
| Component | Description |
|---|---|
| Router | Directs traffic into the cluster. |
| Frontend | Serves the user interface. |
| Backend | Acts as the control plane for Lightrun. |
| Keycloak | Manages authentication. |
| Redis | Handles caching and pub/sub channels (can be local or external). |
| MySQL | Stores application data (can be local or external). |
| RabbitMQ | Optional Manages the event message queue, primarily for sending telemetry to Lightrun (local or external). |
| Datastreamer | Optional Sends audit logs to various SIEM systems. |
If you just want to get Lightrun up and running with default settings, start with our Quick Start Guide. This guide covers all the essential steps for a basic installation.
For a production-ready deployment, refer to the Step-by-Step Planning for Production section to ensure security, scalability, and best practices.
To ensure a smooth and secure production deployment of Lightrun, follow these key planning steps:
- Assess expected resource usage (CPU, memory, storage) and plan for scalability. More info on Capacity Planning
- Review the Compatibility matrix for the supported tools. More info on Compatibility
- Decide whether to use Helm-managed secrets or an external secrets manager. More info on Secrets Management
- Plan how Lightrun certificate will be issued and managed for secure communications. More info on Certificate
Tip
Use external database
- Choose between a local or external database. More info on Database Setup
- Decide how external traffic will reach the Lightrun router (Ingress, Service, OpenShift Route). More info on Router
- Choose where to store and manage container images (e.g., private registry, Docker Hub, Azure Container Registry, AWS ECR). More info on Container Image Registry
Tip
Use external redis
- Determine if Redis will be local or external. More info on Redis Setup
- Determine if RabbitMQ is needed for sending telemetry to Lightrun. More info on RabbitMQ
- Establish network policies to restrict access between services and prevent unauthorized communication. More info on Network Policy
- Decide whether internal TLS is necessary for secure component communication. More info on Internal TLS
Decide where to run your Kubernetes cluster based on your infrastructure needs. Consider whether you’ll deploy all services locally (including RabbitMQ, Redis, and MySQL) or use managed cloud services.
Select your preferred cloud provider for deployment:
Review the Known Limitations before deployment.
Check the versions mapping documentation for version compatibility.
Check the release strategy for the meaning of major minor patch.
See the changelog for a detailed history of changes and improvements in each release.