You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Info for the community: Kestra 0.20.0 will be released on December 3rd, following our usual release cycle on the first Tuesday of every second month.
Breaking Changes
Labels starting with system. are now reserved for internal usage so you can no longer use this prefix for your own labels.
EE: fallback on unhealthy workers
By default, a task configured to run on a worker group where no workers are available will wait for the worker to be available. The previous behavior was to fail.
This is configurable, the previous behavior can be implemented with:
- id: hellotype: io.kestra.plugin.core.log.Logmessage: Hello World!workerGroup:
key: wg1fallback: FAIL # possible values are WAIT (default), FAIL or CANCEL
Starting with 0.20, if you are using the Kafka backend, there is no need to start an external indexer, even for the Kafka backend, as the webserver will start an embedded indexer automatically.
However, if you still want to start one, it is still possible to do so and you can disable the webserver embedded indexer by starting it with --no-indexer.
Starting an extra indexer should only be needed for very hight throughput when you want the UI to be updated with very low latency about execution information, most of the time the webserver embedded indexer should be enough.
For Kafka backend user
Due to a change in the way we handle plugin defaults, we need to have the flow source available to the Kestra Executor.
For those who use our Kafka backend, this must be done by executing the following command:
Info for the community: Kestra 0.20.0 will be released on December 3rd, following our usual release cycle on the first Tuesday of every second month.
Breaking Changes
Labels starting with
system.
are now reserved for internal usage so you can no longer use this prefix for your own labels.EE: fallback on unhealthy workers
By default, a task configured to run on a worker group where no workers are available will wait for the worker to be available. The previous behavior was to fail.
This is configurable, the previous behavior can be implemented with:
EE Users
Make sure to run the following CLI command to copy email as username https://github.com/kestra-io/kestra-ee/issues/1587
auths users email-replace-username
Kafka ElasticSearch indexer
Starting with 0.20, if you are using the Kafka backend, there is no need to start an external indexer, even for the Kafka backend, as the webserver will start an embedded indexer automatically.
However, if you still want to start one, it is still possible to do so and you can disable the webserver embedded indexer by starting it with
--no-indexer
.Starting an extra indexer should only be needed for very hight throughput when you want the UI to be updated with very low latency about execution information, most of the time the webserver embedded indexer should be enough.
For Kafka backend user
Due to a change in the way we handle plugin defaults, we need to have the flow source available to the Kestra Executor.
For those who use our Kafka backend, this must be done by executing the following command:
The text was updated successfully, but these errors were encountered: