# best-practices

08/16/2022, 5:08 AM
running prefect v1.0 on aks and can't figure out how to use multiple nodepools - any tips or tricks here? I'd like to have an agent per nodepool, where nodepools have different sized nodes. Any insight or help here would be great! Currently I have 2 aks clusters, one with a nodepool of small nodes (4 cores, 16gb memory) and one with a nodepool of medium nodes (16 cores, 64gb memory).

Anna Geller

08/16/2022, 10:54 AM
maybe someone from the community will chime in, but it's hard to give such infrastructure recommendations via Community Slack (it depends on your setup, needs, security requirements, scale, and type of work you do), if you need more help, we have infrastructure experts you can reach out via paid support

Mathijs Carlu

08/16/2022, 11:56 AM
I think you can do this by labeling all nodes within a pool with the nodePool name, then create 2 different deployments with the nodeSelector field (Correct me if I'm wrong, still actively learning Kubernetes). One should point to the first pool, the other to the second one. Otherwise, Node affinity might help.
🙏 1

Henning Holgersen

08/16/2022, 7:20 PM
I’m only running one AKS cluster, but with two nodepools where one is very small and always on, and a large one is normally at 0 nodes but if I need it I can run a job specifying the memory requirement and it will spin up. It takes a little time of course, but… basically I have not needed to select nodepools, I can simply request memory. But if you need more granular control, I guess the node affinity linked above is the best way to go, paired with a custom template for the job spec.
🙏 1