-
Epic
-
Resolution: Unresolved
-
Minor
-
None
-
None
-
None
-
Arch for `oc start-build`
-
13
-
False
-
None
-
False
-
Not Selected
-
NEW
-
To Do
-
NEW
Description of problem:
After creating a "buildconfig", the "oc start-build <buildconfig-name>" can be used to start a new build. I have a OCP 4.14 cluster with both x86 and s390x worker nodes. I would like to be able to use the "oc start-build" command to choose which nodes a build is scheduled on with the end goal of building images for both s390x and x86 in the same cluster. Nodes can be chosen in a yaml description of a build using the "nodeSelector" field, however, the "oc start-build" command is much more convenient.
Version-Release number of selected component (if applicable):
Client Version: 4.14.0-202312132033.p0.g33a7a8b.assembly.stream-33a7a8b Kustomize Version: v5.0.1 Server Version: 4.14.8 Kubernetes Version: v1.27.8+4fab27b
How reproducible:
Reproducible
Steps to Reproduce:
1. Create a buildconfig on an OCP 4.14 cluster with two architectures 2. Run "oc start-build <buildconfig-Name>" 3. Use "oc get pods -o wide" to see which nodes the builds are scheduled on 4. Repeat steps 2 and 3 multiple times noting which nodes the build is scheduled for and that it is not consistent
Actual results:
Builds scheduled on any node
Expected results:
Builds scheduled on selected nodes
Additional info:
Feel free to let me know if this is not the right location for this request.