Generally, applications often need to pull a lot of dependencies during the build process. It might cause some issues like long pulling time, or unstable network causing failure. In order to make build robust, and to speed up the build by using cache, we recommend you configure one or a set of CI nodes which the system schedules the task of CI/CD pipelines or S2I/B2I builds running on.
adminaccount, navigate to Platform → Infrastructure.
node2and enter its detailed page. Click More → Edit Labels.
ci, click Save.
Note the node may already have the key with empty value. You can just change the value to
Basically, pipelines and S2I/B2I workflows will be scheduled to this node according to the Node affinity. If you want to make CI nodes as the dedicated ones, which means these nodes are not allowed other workloads to be scheduled to them, you can follow with the steps below to set Taint.
node.kubernetes.io/ciwithout specifying value. You can choose
PreferNoScheduleat your will.