A deep dive into executor observability, helper image resolution, configuration expansion, and CI trace logging in Go.

GitLab Runner uses helper images to perform several internal operations during CI job execution, including source retrieval, cache handling, and artifact management.

When running jobs through the Kubernetes executor, the helper image is particularly important because it runs as part of the job's execution infrastructure.

However, there was an observability gap: when users configured a custom helper_image , the Kubernetes executor did not expose the selected helper image directly in the CI job trace.

This made debugging container image configuration more difficult than necessary.

I addressed this behavior in GitLab Runner Merge Request !7778 , resolving Issue #2387 .

This article explores the underlying problem, the difference between runner debug logging and job trace logging, the implementation, configuration edge cases, and the regression tests added to verify the behavior.

1.…