GitLab 14.2 Release Kickoff, 15 Jul 2021

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: GitLab 14.2 Kickoff - Enablement:Distribution

Description

Kickoff for the 14.2 milestone for the GitLab Distribution team.

Planning Issue: https://gitlab.com/gitlab-org/distribution/team-tasks/-/issues/857

A

Hello: everyone, my name, is dylan reno and I'm the product manager for distribution, and today I'm going to be discussing our kickoff for our 14.2 release.

A

This is our scheduling issue, pretty streamlined similar to our last few milestones again, we're still cruising along on our operator. Ga, of course we will work on any rollover, work from 14.1 and then finally, we would like to loop in a little bit of tech debt, it's still a motivator for us to accomplish a little bit of tech debt every milestone, and that is still true for this milestone as well.

A

So jumping right into a couple of the issues related to the operator. I wanted to discuss our operator installation options which was evaluated last milestone and, and I believe we have a path forward by utilizing a customized route. This allows a lot of benefits.

A

Potentially, a git lab, you know, kube ctl, apply command, might be a little bit complicated and creating that manifest yaml file was going to be slightly more complicated, so utilizing customize potentially will offer a lot of benefits so for now this is the path we are proceeding along and we're going to continue to research.

A

If customize is the right path for us, another.

A

Issue related to the operator that I'd like to mention this, this milestone is going to be running our functional qa tests, our functional and qa tests. Excuse me for the operator on a kubernetes cluster, so just making sure everything is buttoned up nicely to run well in kubernetes a couple controller, op issues here. One is: we want to be capable of disabling our included redis and, uh allowing you know, users to use an external redis. So this is a, uh I think, a big benefit to users, and the same goes for postgres sql.

A

So we want to allow users to disable the included database and use one that they they would like to provide themselves. So I think, really great additions coming along in this milestone for the operator as we get closer and closer to ga again, the big one was evaluating our operator installation options for the last one and now being able to capitalize on that work, so great job to everyone on the team.

A

A couple petroni issues that we're going to be tackling this milestone. One is allow list support, so this is uh added uh from petroni. So we would like to also include it for support in the omnibus and another one. That's related to petroni is tls certificates, so both of these are available for patrony, so we would like to also offer those options to users. Ultimately, finally, we are still working on this issue which might be familiar to some folks. This is more of a long tail.

A

uh You know managing omnibus configuration secrets is a large operation and uh we're slowly consuming a couple issues here and there. I think this will pick up a little bit more once the operator is ga, but one of the issues that we're going to be working on this milestone is encrypting all rails passwords stored in gitlab.rb.

A

This is quite a bit of customer interest on this one and we want to deliver that value back to the customers so that they are feeling more secure and their rails passwords that are being stored in gitlab.rb, so that is our kickoff for 14.2. Thank you very much and have a great day.