GitLab 14.10 Release Kickoff, 18 Mar 2022

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: GitLab 14.10 Kickoff - Enablement:Distribution

Description

Kickoff for the Distribution group for the GitLab 14.9 release.

Planning issue - https://gitlab.com/gitlab-org/distribution/team-tasks/-/issues/1010#product-priorities

A

Hello: everyone, my name, is dylan reno, the product manager for distribution here at gitlab and today I'll be kicking off our 14.10 release.

A

So first up here is our scheduling issue and our product priorities listed at the top we're going to be tackling cloud native fips compliance which you just saw um red hat operator, certification, long-term bill efficiency and specifically an investigation for parallelizing, our omnibus builds and secrets configuration so moving into a little more details. Again. This is a familiar issue that you might have seen from our last kickoff video.

A

We had our investigation issue scheduled for 14.9 and from that investigation issue we have created two new items that we'll be hopefully tackling in 1410..

A

Moving on to our official red hat certification, we renamed this issue to official red hat marketplace, listing and decoupled the actual certification from the marketplace listing. So we're going to work towards certification um in this time and the actual marketplace listing will be a fast follow. After, but first up we will be ensuring all container images have ubi variants which we'll work on in 1410 and then a follow-up of that will be actually you know having the operator, deploy those ubi images and having them certified.

A

So um these two kind of go hand in hand, and then you know once that's complete, hopefully we'll be certified, and then you can see the issue here is: actually you know being deployed from the openshift marketplace.

A

So moving on to our long-term bill efficiency project, um this milestone. We want to complete a spike uh on our idea to paralyze omnibus building and reduce omnibus upgrade diffs. So what this means is it's a lot of efficiency internally, but also customers will see this as a efficiency as well for no longer necessarily needing to download the entire omnius package every time they upgrade.

A

So this is um hopefully a big upgrade and um you know we'll see dividends not only for customers specifically on this issue, but the time we save in testing will allow us to work on more customer related features.

A

So next up uh related to our secure solution for managing omnibus secrets. um This is a specific issue for encrypting all rails passwords, which we've talked about before and we're just going to continue moving down this list for the other passwords that are stored in gitlab.rb.

A

So, moving on um a couple more that I want to uh mention that are big issues for tackling 1410 is actually kicking off our migration to sync, and so we want to upgrade to the latest version and test uh sync. um So that'll kind of kick off this project, another uh kind of exciting one, uh all right, it's a very exciting one is providing packages for raspberry pi for bullseye. Now that bullseye's out, we want to be able to provide packages for raspberry pi, just like we do for our other distributions.

A

Next up is supporting backups with azure blob storage, so we have customers who are interested in actually using azure blog storage as their backend, and so we want to provide a solution for that.

A

Next up is actually adding alma linux for as a build image, and this follows our work that we've already done for adding packages for all the linux due to the end of life of centos 8., and ultimately, this will fall into our epic for actually using all the linux as a base builder.

A

So this is, you know, a nice, a nice little segue to that work from actually moving away from centos 8 due to its end of life.

A

So next up is supporting multiple pg bouncer instances on the same port. So this was an investigation. It was it was completed a mile soon or two ago, and that has developed into this work which we're going to be completing in 1410, which is actually implementing multiple pg pg bouncer instance on a single node.

A

So what this means is this was a bottleneck for actually only using a single port or a single node um in a single instance of pg bouncer, um not only a generic generic bottleneck, but also for implementing um your repeatable database provisioning.

A

So this will be a nice little upgrade and finally, as a general sort of internal work that we want to do in setting up our major release is check all removals marked for 15.0 ensure they have deprecations warnings in place actually in the product. So we've announced these with our release posts, but we want to ensure that actually, within the upgrades that this will show up- and so this is just setting us up well for a nice smooth major release for customers- that is all for our 14.10 release.

A

Thank you so much and have a good rest. Your day.