Epic Goal

Provide experiences that let developers control which node a build is scheduled on, using Node Selectors.

This was spun out of BUILD-985 thanks to upstream Shipwright contributions!

Why is this important?

• Build behavior can change significantly based on the OS/architecture of the scheduled worker node. Clusters with multiple worker node architectures may need to specify that builds run on specific note OS/architecture.
• Some applications - such as AI "Build" workloads - may need access to nodes with specialized hardware.
• Clusters that run CI and application workloads side by side may want to separate "Build"/CI workloads (which consume resources in bursts) from application workloads that have uptime/steady resource requirements.

User Stories

1. As a developer, I want builds to run on larger nodes with more CPU/memory so that my builds run faster
2. As a developer, I want my ARM-specific applications to run natively on ARM worker nodes.
3. Multipurpose/multi-tenant clusters

Acceptance Criteria (Mandatory)

• Builds can use node selectors to specify where builds run
• Developers can specify the node selectors for a build via the CLI

Dependencies (internal and external)

1. Tekton support for Pod Template tuning.

Previous Work (Optional):

1. BUILD-972 - enhancement proposal for build scheduler options (see also SHIP-0039)

Open questions::

• Which version of Shipwright will have this? Builds v0.14.0 for the node selector feature.

Done Checklist

• Acceptance criteria are met
• Non-functional properties of the Feature have been validated (such as performance, resource, UX, security or privacy aspects)
• User Journey automation is delivered
• Support and SRE teams are provided with enough skills to support the feature in production environment