Description
What would you like to be added:
sig-release maintains build and fast-build jobs to periodically build and publish kubernetes artifacts. These jobs also update their respective version markers. When other jobs run, they determine the version of Kubernetes to download by fetching the latest version marker for a particular version. Some of these jobs use the latest "fast" version and some use just the latest. In practice, the only time we need to use a non-fast version is when we are testing an os/arch combo other than linux/amd64, but there are a number of jobs that use non-fast version even though it is not required (example: kubernetes/kubernetes#96463 (comment)).
Why is this needed:
Using a non-fast build is not necessarily wrong, but it does result in a stale build being used when a perfectly valid new one is available. We should always use fast-build when appropriate. However, it is difficult to enforce this as the version marker being used is not always surfaced in the prowjob config. In order to enforce usage of a particular version marker, jobs must utilize frameworks such as kubetest where the version is selected in a standardized manner.
Work in this area is related to kubernetes/release#1711 and kubernetes/community#5014.
/cc @justaugustus @saschagrunert @kubernetes/release-engineering
/assign