It seems there are no direct hits specifically addressing how a Kubernetes worker chooses the node pool to submit a pod to in the Prefect documentation or GitHub issues. However, we can glean some useful information from the related documentation on
Kubernetes workers and
work pools.
### Key Points:
1.
Declarative Infrastructure Syntax: Kubernetes workers use infrastructure as code (IaC) patterns to create the execution environment, often employing template variables to customize the Kubernetes manifest.
2.
Work Pools: Configurations in the Prefect UI or via CLI commands can list and manage work pools, which are essential for controlling the environment where workers operate.
You might need to inspect your Kubernetes worker's specific configuration for node selection logic. Look into whether you're using Prefect manifests that define node selectors or affinity rules.
### Documentation Links:
-
Developing a New Worker Type
-
Kubernetes Deployment Guide
-
Managing Work Pools
For a deeper dive, you may need to look into the relevant Prefect worker configuration in your deployment, or check the source code if further customization is required.