[K8S Dogfooding] Restructure UBI images to allow each separate gitlab-runner commit to be deployed.
UBI images are currently structured so that binaries are fetched from either main or release tag, nothing else. This makes it impossible to deploy each commit into gitlab-runner's main branch because at the time of running the ubi pipeline we can't be sure which binary is being picked up.
We have the following options:
- Push binaries to S3 under each separate commit, they are currently pushed under
mainonly orrelease tag. This will require more bandwidth and storage but is the simplest solution - Restructure the parent gitlab-runner pipeline to run the child ubi-images pipeline so that it downloads the artifacts from the parent pipeline's
binariesjob. I've attempted this at Run ubi images with BUILD_COMMIT_SHA and PARENT... (!5244 - merged) • Georgi N. Georgiev | GitLab • 17.9 and Build branch manifests with correct commit sha (gitlab-org/ci-cd/gitlab-runner-ubi-images!53 - merged) • Georgi N. Georgiev | GitLab • 17.9 but am having trouble with the child pipeline finding the parent pipeline's artifacts - Restructure the way OCP images are built and put them into the gitlab-runner project. With the latest changes to how images are built this might be the easiest approach but will couple our images into a single project even more.