Prerequisites: software and hardware requirements before deploying Kestra

This page outlines the software and hardware requirements for running Kestra.

Software requirements

The table below lists the software requirements for Kestra.

Java Runtime

Queue and Repository

Kestra Open Source supports PostgreSQL or MySQL for the queue and repository components.

Kestra Enterprise Edition (EE) provides two options:

• Use the same JDBC configuration as Open Source for standard deployments
• Use Kafka with Elasticsearch or OpenSearch for large-scale deployments

MySQL settings

MySQL deployments need two settings that MySQL does not apply by default.

Transaction isolation level. Kestra requires the READ COMMITTED transaction isolation level. MySQL defaults to REPEATABLE READ, which can cause deadlocks in Kestra’s JDBC queue. When a connection uses a different level, Kestra raises IllegalStateException: Isolation level must be READ COMMITTED.

Set the level on the MySQL server in your option file (my.cnf), then restart MySQL:

[mysqld]
transaction_isolation=READ-COMMITTED

On a managed service such as Amazon RDS or Cloud SQL, set the transaction_isolation parameter in the parameter group or database flags instead.

If you cannot change the server configuration, set the level for Kestra’s connections in the datasource configuration:

datasources:
  mysql:
    url: jdbc:mysql://localhost:3306/kestra
    driver-class-name: com.mysql.cj.jdbc.Driver
    username: kestra
    password: k3str4
    dialect: MYSQL
    transaction-isolation: TRANSACTION_READ_COMMITTED

Time zone tables. Load the MySQL time zone tables. If the time zone data is missing, the scheduler can misfire or skip runs. Follow the MySQL guide to load the time zone tables.

Internal Storage

Hardware requirements

A Kestra standalone server requires at least 4 GiB of memory and 2 vCPUs. To use script tasks, the server must support Docker-in-Docker (this is why, for example, AWS ECS Fargate is not supported).

For guidance on allocating memory and CPU for different architecture components, contact us. We can help size your deployment based on your expected workload.