UNCLASSIFIED - NO CUI

Update Ironbank to v19

This MR contains the following updates:

Package Update Change
gitlab-runner minor 0.88.30.91.2
gitlab-runner-app-version major 18.11.319.2.2
gluon minor 1.1.11.1.6
bb-common minor 1.0.21.4.0
registry1.dso.mil/gitlab/gitlab-org/gitlab-runner major v18.11.3ubi-fips-v19.2.2
registry1.dso.mil/gitlab/gitlab-org/gitlab-runner/gitlab-runner-helper major v18.11.3ubi-fips-x86_64-v19.2.2

Complete MR checklist

Assignee

  • Followed upgrade instructions outlined in docs/DEVELOPMENT_MAINTENANCE.md
  • Update Docs with new/updated steps as needed
  • Tested and Validated Changes made with supporting info like logs or screenshots from test pipelines

Add supporting info below

01-k9s-helmrelease 02-k9s-pods 03-source-sha 04-runner-image 05-gitlab-runner-online 06-gitlab-pipeline-passed 07-gitlab-19.1.3-version

Reviewer only

  • Tested and Validated changes

Configuration

📅 Schedule: (UTC)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻️ Rebasing: Whenever MR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this MR and you won't be reminded about these updates again.


  • If you want to rebase/retry this MR, check this box

This MR was automatically generated by Renovate Bot.

Upgrade Notices

GitLab Runner 19 is a major-version upgrade from 18.11.3 to 19.2.2; it does not upgrade the GitLab application.

  • Consumers using FF_HASH_CACHE_KEYS=true with distributed cache should expect existing cache objects to become unreachable because Runner 19 adds a shard prefix to object paths. Keep the flag consistent across runners sharing a cache and expect cache misses and cache rebuilds after upgrading. See the upstream cache key handling guidance.
  • GitLab Runner manager and helper images move from Iron Bank to Verified Publisher UBI/FIPS images under registry1.dso.mil/gitlab/gitlab-org/gitlab-runner and registry1.dso.mil/gitlab/gitlab-org/gitlab-runner/gitlab-runner-helper. No separate Runner configuration or data migration is required for this image-source change, but Registry1 credentials, mirrors, policies, and allowlists must permit the new paths. Update custom image overrides and keep the manager and helper versions aligned per the upstream helper-image guidance.
  • Review the upstream GitLab Runner 19.2.2 release and Runner changelog for site-specific impacts.

Linked issues

Closes #220 (closed)

Edited by Matt Vasquez

Merge request reports

Loading