It seems there isn't a strict naming convention defined in the Prefect documentation for work pools. However, from the available examples, you can opt for a meaningful and descriptive name based on the type or purpose of the pool.
For example:
-
docker-pool: for Docker-based work pools
-
k8s-worker-pool: for Kubernetes worker pools
-
high-priority-tasks: for work pools handling high-priority tasks
The focus should be on clarity and ease of identification. You can refer to the
Prefect documentation on work pools for more details.