Skip to content

Reuse to hardcoded variables for container registry

David Dieulivol requested to merge ddieulivol-fix_registry_variables_for_deploy_image into master

What does this MR do and why?

Fixes the image name (see !1706 (comment 1133190678) for context).

Tested locally with docker pull registry.gitlab.com/gitlab-org/gitlab-build-images/ruby-3.0:gcloud-383-kubectl-1.23-helm-3.5:

$ docker pull registry.gitlab.com/gitlab-org/gitlab-build-images/ruby-3.0:gcloud-383-kubectl-1.23-helm-3.5                                                                                            
registry.gitlab.com/gitlab-org/gitlab-build-images/ruby-3.0:gcloud-383-kubectl-1.23-helm-3.5: resolved       |++++++++++++++++++++++++++++++++++++++| 
manifest-sha256:1a4d3e226fa8fa83452f0311c66058e568dc7a708442c11c58ea986767344613:             exists         |++++++++++++++++++++++++++++++++++++++| 
config-sha256:3d51d7b7c7000872820c0bf5006ffa6cddf59ed8b8cde4be2737598d4998021c:               exists         |++++++++++++++++++++++++++++++++++++++| 
layer-sha256:4f4fb700ef54461cfa02571ae0db9a0dc1e0cdb5577484a6d75e68dc38e8acc1:                exists         |++++++++++++++++++++++++++++++++++++++| 
layer-sha256:b6d6a76ebdbe1e858fec4564af6c6c3fe9e9bf1c502c8c8a51afd0fcf3374d44:                done           |++++++++++++++++++++++++++++++++++++++| 
layer-sha256:acba011925eea367d8379d0aa97047399fccb17543bedfa17a6fbb2b34234b14:                exists         |++++++++++++++++++++++++++++++++++++++| 
layer-sha256:c2c14659911890c8140dba847f7bba8f615efe697164e2ba987f92205bac452a:                done           |++++++++++++++++++++++++++++++++++++++| 
layer-sha256:edc05f4a42f6f494f6620ec6eb8e4e5e0bc16a8271214d2d9b2078cde6255d5f:                done           |++++++++++++++++++++++++++++++++++++++| 
layer-sha256:f0a8441b68a557da47d4fafe2c3b679c08e69ca0e6951c3752fe6e7bcd275d18:                done           |++++++++++++++++++++++++++++++++++++++| 
layer-sha256:8f82c7b3a588cf9a05fa6e3e6c13f49934444e6b591dddd9a8fe0a76f5e57d1f:                done           |++++++++++++++++++++++++++++++++++++++| 
layer-sha256:0d0f0dc8a61aa12a50b263292a2c650baa5cfbcb349d38f6382afb26bc199984:                done           |++++++++++++++++++++++++++++++++++++++| 
layer-sha256:36bba29f59fef7052a8ffe75a0f84e1af1e975dd0f0f4747b78696d715547a45:                done           |++++++++++++++++++++++++++++++++++++++| 
elapsed: 66.6s                                                                                total:  581.7  (8.7 MiB/s)

Action items

  • (If applicable) Add documentation to the handbook pages for Triage Operations =>
  • (If applicable) Identify the affected groups and how to communicate to them:
    • /cc @person_or_group =>
    • Relevant Slack channels =>
    • Engineering week-in-review

Merge request reports