Loïc Mathieu
Loïc Mathieu
### Describe the issue RESTARED tasks goes directly to RUNNING but we check concurrency limit only on CREATED tasks. ### Environment - Kestra Version: 0.18.0-SNAPSHOT - Operating System (OS/Docker/Kubernetes): -...
### Feature description When you have a task with a `-` in it, you cannot refer it via its variable name as Pebble use the `-` for substraction, if you...
Currently we use 2 thread for each worker job: - One thread of the main executorService which is used immediately after queue consumption to not block the queue. It also...
### Describe the issue The calls to the API for the logs widget on the dashboard are made twice. Goes to: http://localhost:8080/ui/dashboard You'll notice that the calls to /logs/search and...
### Feature description Currently, you can pass execution labels when starting an execution from the UI/API or a Webhook. But you cannot do that from a Trigger as triggers automatically...
Operators deployed using the generated k8s resources are forbidden to access the CRD. Steps to reproduce: - Build the orchestrator - Deploy the CRD using the generated CRD resource -...
There is only a documentation to deploy the operator using OLM which is not the most common way to deploy an operator in a Kubernetes cluster. It would be great...
### Issue description With the new `io.kestra.plugin.transform.grok.TransformValue` task from the [Plugin Transform,](https://github.com/kestra-io/plugin-transform/blob/main/plugin-transform-grok/src/main/java/io/kestra/plugin/transform/grok/TransformValue.java) we can replace Logstash by Kestra! A blueprint would be great to see how we can handle a...
**Describe the bug** When using `--quiet` only error logs should be displayed. But when using a JShell script two logs are still emitted when launching JBang from Docker: ``` Aug...
Fixes #4688 Flow example: ```yaml id: myflow namespace: company.team tasks: - id: hello type: io.kestra.plugin.core.log.Log message: Hello World! 🚀 logToFile: true ``` When run, the log is in a file...