After using app.scheduling.nodeSelector, the pod for 'kong' didn't follow the selector config #10319
Description
What happened?
After using app.scheduling.nodeSelector, the pod for 'kong' didn't follow the selector config
k8s-worker01-03 is expected node to hold the pod.
k8s-worker04-06 is not expected to hold the pod.
kubernetes-dashboard kubernetes-dashboard-api-7d985b8468-drjr2 1/1 Running 0 15s 192.169.79.87 k8s-worker01
kubernetes-dashboard kubernetes-dashboard-auth-74b698f4d8-5tv9w 1/1 Running 0 15s 192.169.39.221 k8s-worker03
kubernetes-dashboard kubernetes-dashboard-kong-648658d45f-ghxlr 0/1 Running 0 15s 192.169.38.77 k8s-worker06
kubernetes-dashboard kubernetes-dashboard-metrics-scraper-7f598658dc-jqgb2 1/1 Running 0 15s 192.169.39.220 k8s-worker03
kubernetes-dashboard kubernetes-dashboard-web-8667d9565b-bxcpf 1/1 Running 0 15s 192.169.79.88 k8s-worker01
What did you expect to happen?
the pod for 'kong' should follow the selector config
How can we reproduce it (as minimally and precisely as possible)?
helm upgrade --install kubernetes-dashboard kubernetes-dashboard/kubernetes-dashboard --create-namespace --namespace kubernetes-dashboard
--set app.scheduling.nodeSelector.network_security_level="internal" ##Optional:nodeSelector
`
Anything else we need to know?
No response
What browsers are you seeing the problem on?
No response
Kubernetes Dashboard version
kubernetes-dashboard-7.13.0
Kubernetes version
v1.33.3
Dev environment
No response