Management Endpoint Hardening
For the complete documentation index, see llms.txt. For a full content snapshot, see llms-full.txt. Append.mdto anykestra.io/docs/*URL for plain Markdown.
Kestra 2.0 hardens the default configuration of the management port (8081). Several settings that were permissive in 1.x have been removed or reversed.
What changed
| Setting | 1.x default | 2.0 default |
|---|---|---|
endpoints.all.sensitive | false (all endpoints open) | Micronaut default (true) |
endpoints.env.enabled | true | false |
endpoints.health.details-visible | ANONYMOUS | AUTHENTICATED |
endpoints.loggers.write-sensitive | false (unauthenticated writes) | true |
/worker endpoint sensitivity | false (open) | true (sensitive) |
/scheduler endpoint sensitivity | false (open) | true (sensitive) |
| docker-compose port mapping | 8081:8081 exposed | commented out |
Who is affected
You are affected if any of the following apply:
- You query
/envon the management port (e.g., from a monitoring agent or automation script). - You call
POST /loggersto change log levels at runtime without any authentication. - You poll
/workeror/scheduleron the management port from tooling that does not send credentials. - You rely on anonymous health details at
/health. - You use the
docker-compose.ymlbundled with Kestra to expose the management port.
How to restore the previous behavior
If your environment relies on the old defaults, you can opt back into each setting individually in your application.yml:
endpoints: all: sensitive: false # re-opens all endpoints for unauthenticated access env: enabled: true # re-enables the /env endpoint health: details-visible: ANONYMOUS # shows health details to unauthenticated requests loggers: write-sensitive: false # allows unauthenticated logger level changes worker: sensitive: false # re-opens the /worker endpoint scheduler: sensitive: false # re-opens the /scheduler endpointFor the docker-compose setup, uncomment the management port mapping in docker-compose.yml:
ports: - "8081:8081"Re-opening these endpoints restores the previous behavior but also restores the associated security risks — unauthenticated access to environment variables, the ability to change log levels, and exposure of running task and trigger details. Only opt back in if you understand the implications and can restrict access at the network layer.
See Management endpoint access for the recommended hardening approach.
Was this page helpful?