Manage Kestra Worker Queues with the Terraform Provider
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.
Terraform Resource: kestra_worker_queue
Manages a Kestra Worker Queue. Worker Queues route tasks to Worker Groups through their tag set; Worker Groups subscribe to them via the kestra_worker_group resource.
This resource is only available on the Enterprise Edition
Example usage
resource "kestra_worker_queue" "example" { queue_id = "gpu-queue" name = "GPU Queue" description = "Routes GPU workloads to dedicated workers" tags = ["gpu", "high-memory"]
# Optional: restrict the queue to specific tenants allowed_tenants = ["production"]}Schema
Required
queue_id(String) The Worker Queue identifier (RFC 1123 label: lowercase alphanumerics and hyphens, must start and end with an alphanumeric, max 64 chars). Used as the routing identity; immutable. Thedefaultandsystemids are reserved.tags(Set of String) The canonical tag set of the Worker Queue (each tag is an RFC 1123 label). Must not be empty, and must be unique across Worker Queues together withallowed_tenants.
Optional
allowed_tenants(Set of String) The tenants allowed to use the Worker Queue. Omit for an unrestricted queue.description(String) The Worker Queue description.name(String) The Worker Queue human-readable name.
Read-Only
id(String) The Worker Queue id.
Import
Import is supported using the following syntax:
The terraform import command can be used, for example:
terraform import kestra_worker_queue.example {{queue_id}}Was this page helpful?