When I build the Jenkins pipeline job, sometimes the Jenkins log will show ‘There are no nodes with the label’ xxxx ', which will stick here for 4-5 minutes without any output, resulting in low efficiency. What is the reason for this?
Could this be linked to insufficient Kubernetes resources?
Ensure that your Kubernetes cluster has enough resources (CPU, memory, etc.) to accommodate the Jenkins agents.
If the cluster is overloaded or lacks available resources, Jenkins may struggle to provision nodes with the specified label, resulting in delays.
My $0.02 (I haven’t installed Jenkins through Kube yet).
Thank you for your answer!@poddingue My k8s cluster resources are sufficient. When “there are no nodes with the label” waiting for a long time, my k8s cluster did not create a Jenkins agent.When I wait for 4-5 minutes, the Jenkins agent will be created, and I don’t know what happened during this period.