AKS
AKS copied to clipboard
Azure
[BUG] Scaling from 0->X doesn't work when relying on RuntimeClass
Describe the bug I have a windows node pool set the a minimum of 0 and max of 50 so the pool is available if a Windows workload is needed. I set the nodeSelector and tolerations in the RuntimeClass and assign it to the Windows workload. This doesn't result in a scale up event. When I apply the settings directly to a deployment, the node pool scales up as expected.
To Reproduce Steps to reproduce the behavior:
- Create a windows node pool that can scale to 0. Let it scale down to 0.
- Create the following RuntimeClass
apiVersion: node.k8s.io/v1
handler: runhcs-wcow-process
kind: RuntimeClass
metadata:
name: windows-2019
scheduling:
nodeSelector:
kubernetes.io/os: windows
tolerations:
- effect: NoSchedule
key: os
operator: Equal
value: windows
- Create a windows workload and assign that RuntimeClass to it. It will not scale up the node pool
- Delete the RuntimeClass from your workload and apply the nodeSelector and tolerations directly to the workload. The node pool will scale up.
Expected behavior The node pool should scale up based on RuntimeClass rules.
Environment (please complete the following information):
- Kubernetes version 1.24.6
![microsoft-github-policy-service[bot] avatar](https://avatars.githubusercontent.com/in/95686?v=4 "Published by a pub.dev verified publisher"){kind=small}