Wait for MR image before starting runner incept

Romuald Atchadé - OOO until Jan 11th, 2026requested to merge
runner-incept-wait-for-images into main

What does this MR do?

Runner Incept run an GitLab Runner Helm Chart test where the Helm Chart is used to install an MR image. A "Hello World" job is then run against this Runner Manager.

It happens that the Helm Chart test starts before the MR images are deployed, causing the Helm Chart installation to fail as in this job log https://gitlab.com/gitlab-org/ci-cd/tests/runner-incept/-/jobs/9756715428

kubectl log 
[...]
NAME                             READY   STATUS             RESTARTS   AGE    IP           NODE                 NOMINATED NODE   READINESS GATES
gitlab-runner-568658987f-fmvq6   0/1     ImagePullBackOff   0          110s   10.244.0.2   kind-control-plane   <none>           <none>
NAME                             READY   STATUS         RESTARTS   AGE    IP           NODE                 NOMINATED NODE   READINESS GATES
gitlab-runner-568658987f-fmvq6   0/1     ErrImagePull   0          113s   10.244.0.2   kind-control-plane   <none>           <none>
NAME                             READY   STATUS         RESTARTS   AGE    IP           NODE                 NOMINATED NODE   READINESS GATES
gitlab-runner-568658987f-fmvq6   0/1     ErrImagePull   0          117s   10.244.0.2   kind-control-plane   <none>           <none>

This MR aims to prevent it by starting the incept tests only when the images are pushed successfully

Why was this MR needed?

Prevent stuck jobs in Runner Incepts

What's the best way to test this MR?

Pipeline passes ✅

What are the relevant issue numbers?

Merge request reports