Problem Background
I have a public network cluster, but some nodes have poor network connectivity, causing them to fail to pull images. This frequently leads to image pull failures or other network issues. However, its performance is excellent, so I want CI pods to run on other nodes and not be scheduled to this particular node.
Try the following steps
Added to the values.yaml file
components:
ciRunner:
nodeSelector:
ci: "true"
jpsb Ready control-plane 206d v1.33.2 beta.kubernetes.io/arch=amd64,beta.kubernetes.io/os=linux,ci=true,kubernetes.io/arch=amd64,kubernetes.io/hostname=jpsb,kubernetes.io/os=linux,node-role.kubernetes.io/control-plane=,node.kubernetes.io/exclude-from-external-load-balancers=
I then updated and released it.However, it was still scheduled to a node with network problems.I also configured the pod to allow it to be scheduled to the control plane.
Q:
What methods can I use to modify the CI-pod scheduling to a specific node?
Problem Background
I have a public network cluster, but some nodes have poor network connectivity, causing them to fail to pull images. This frequently leads to image pull failures or other network issues. However, its performance is excellent, so I want CI pods to run on other nodes and not be scheduled to this particular node.
Try the following steps
Added to the values.yaml file
I then updated and released it.However, it was still scheduled to a node with network problems.I also configured the pod to allow it to be scheduled to the control plane.
Q:
What methods can I use to modify the CI-pod scheduling to a specific node?