Bump Container Registry to v3.9.0-gitlab
What does this MR do?
3.9.0 (2021-08-18)
Features
- handlers: enable migration mode to be paused (9d43c34)
Related issues
gitlab-org/container-registry#436 (closed)
Checklist
See Definition of done.
For anything in this list which will not be completed, please provide a reason in the MR discussion
Required
-
Merge Request Title, and Description are up to date, accurate, and descriptive -
MR targeting the appropriate branch -
MR has a green pipeline on GitLab.com
Expected (please provide an explanation if not completing)
-
Test plan indicating conditions for success has been posted and passes -
Documentation created/updated -
Integration tests added to GitLab QA -
The impact any change in container size has should be evaluated
Merge request reports
Activity
assigned to @hswimelar
added typefeature label
changed milestone to %14.3
added Container Registry MigrationPhase 1 priority2 labels
added sectioncore platform label
mentioned in merge request gitlab-org/charts/gitlab!2142 (merged)
requested review from @WarheadsSE
mentioned in commit c905f62d
added Pick into 14.2 label
@rspeicher Heads up. I've added Pick into 14.2, I was going to manually pick this via MR, but the button dislikes me for some reason.
The "simplest" would be to revert the chart change on the 5-2-stable or pick this into the 14-2-stable here.
Why this will not break customers:
- The chart consumes the image by name not hash, from registry/Chart.yaml:appVersion, thus
gitlab-container-registry:v3.9.0-gitlab
-
gitlab-container-registry:v3.9.0-gitlab
is tagged, built, and present within this projects container registry
Why this is a problem: documented vs included are out of sync.
- The chart consumes the image by name not hash, from registry/Chart.yaml:appVersion, thus
As long as its okay with the registry team. I would rather we backport 3.9.0 into the 14-2-stable branch of CNG. (Note that it won't be in omnibus though).
I feel like from the charts side, we shouldn't: take away 3.9.0 in
5.2.1
being that they already had it in 5.2.0 unless we have a good reason to.Edited by DJ Mountney@twk3
v3.9.0
doesn't have any changes that omnibus users should be using, but ideally we'd have at leastv3.8.0
on 14.2 in omnibus.Edited by Hayley Swimelar
@hswimelar This merge request could not automatically be picked into
14-2-stable
for14.2.1
and will need manual intervention.Create a new merge request targeting the
14-2-stable-patch-1
branch in order to have this MR included in !743 (merged).Please follow the Process for Developers.
removed Pick into 14.2 label
mentioned in merge request !743 (merged)
@WarheadsSE Cherry-picking this MR has merge conflicts. Given that this seems not urgent according to Hayleys comment and we want to get out the 14.2.1 patch ASAP, we'll probably not include this MR. If you still want it back-ported, we can do so with another patch release.
!745 (merged) is open for this.
mentioned in merge request !745 (merged)
removed typefeature label