GitLab GitLab 13.4 Release Product Kickoff, 17 Aug 2020

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: GitLab 13.4 Kickoff - Enablement:Distribution

Description

Highlights for 13.4 include PostgreSQL 12, OpenShift, cloud native maturity, encrypted passwords, Orchestrator, and gitlab.com Kubernetes migration

A

Hi welcome to the 13.4 kickoff for the distribution team. I'm larissa lane, I'm the product manager for distribution, I'm going to be working off our scheduling issue today. This is the link.

A

It's a team task issue 684 and in here I've got listed out the top product priorities for 13.4 and links to relevant ethics and issues for you to follow along.

A

So first thing I'm going to talk about is our progress on adding support for postgres 12.. In the past couple of milestones, we added postgres, 12 and validated upgrading from postgres 11 to 12, and also using postgres 12 with postgres clusters for failover and replication.

A

So the last little bit of work we have remaining here to fully support postgres 12 is to validate it with our helm chart and we've got a couple of issues related to that scheduled for 13.4.

A

After that, we'll be um taking a break from postgres work for a couple of milestones until 13.6, which is the release in which we will default to postgres 12.

A

and just as a reminder, uh postgres 11 will continue to be supported until get lab 14.0 after that, 12 will become the minimum required version.

A

Next up, we've been doing some really great work on supporting running gitlab on openshift, so we've been working very closely with the red hat team. We meet with them every two weeks and they have been progressing work on the get lab operator.

A

The the most recent things they've been working on. There are adding support for backing up gitlab and upgrading git lab with the operator on our side. We've been doing um some investigation into whether we can uh have the operator use the home chart and things are looking really positive there.

A

We did some great investigation into that and found that it's. It looks like something that we'll be able to do, and so in 13.4 uh the focus will be a bit more evaluation of replacing hard-coded objects in the home chart with dynamic ones, which will um will help support being able to use helm chart and the the benefit of that is that, instead of having a third project being the operator where we need to add support for new get lab features.

A

We'll just be able to add that support directly to the helm. Chart like we do today, which will mean that we won't have a potential lag in feature. Parity in the operator.

A

Next up, we are going to be doing some more work on our cloud native maturity, so we've got the cloud native installation as one of our categories and currently it's in the viable maturity level. We have an epic this epic here for removing it from viable to complete.

A

um We were working towards a target of october to reach the complete maturity.

A

We are blocked on supporting pages in the home chart and that work is quite a bit of work being done there to use object, storage for pages, so that work is not looking like it will be completed until next year. So we're moving the target from complete maturity out to mid next year.

A

um We think that we'll still be able to complete the majority of this work by october and just have the pages component, the last remaining item, and once we do get all of the things checked off, except for pages, we'll start work on um moving the cloud native install to the lovable maturity. So we're not going to sit around and wait for pages. We will continue to make progress on the maturity, so there are two things related to the maturity, epic, that we've got scheduled for 13.4.

A

One is adding support for smart cards, and once we get that support in um that will be one of the few remaining known limitations of the helm installed taken care of the other one is we're going to be working on some better documentation.

A

We have an epic in the maturity, epic, that is, for streamlining the chart documentation. So in this milestone we will be adding documentation for the values and usage of the mailroom chart.

A

Next, we did a proof of concept for encrypting the passwords in the gitlab configuration file over the past couple of milestones, and uh we've got an mr in place. It's been going through maintainer review and in 13.4 we'll be looking at what the next steps are to close. That.

A

Workout the orchestrator tool, so this is the tool that automates the deployment and configuration of get lab at large scale and.

A

We we completed the mvp for the orchestrator. A few milestones back, the mvp was um a.

A

Let me just switch over to the epic.

A

All right here we go um so the mvp was targeted at our geo team and enabling them to quickly spin up a scaled instance of get lab with a geo secondary side, so that included three console nodes. Three database nodes, one application, node and support for a secondary site.

A

We have been spending a lot of time over the past few weeks, defining what alpha will be for the orchestrator.

A

So alpha is going to be still for use by internal teams and not for production use, but it will be a tool that can be used by our professional services teams and our support teams for testing features and and troubleshooting customer problems.

A

We have quite a few issues scheduled for this 13.4 milestone that are part of the alpha epic and they are mostly the themed around um efficiency improvements for how the orchestrator runs uh so, for example, ensuring that that the orchestrator is item potent. So, for example, if you run the orchestrator a second time and you've already before running it, you already had a license assigned to the instance.

A

When you run the orchestrator again, it will recognize the license and won't try to assign a license all over again, and the other theme for 13.4 is to add support for the node types that are recommended for the 2000 reference architecture.

A

So I mentioned the node types that were included in the mbp in the 2000 reference architecture. We also have things like load, balancer, redder skiddly and the monitoring node, so we'll be adding support for deploying these node types with the orchestrator.

A

And finally, uh we are migrating gitlab.com over to kubernetes. uh This has been an incremental project. um Traditionally we managed gitlab.com with the omnibus installer and we are migrating one component at a time across two kubernetes.

A

This is a really awesome opportunity for us to identify some limitations of using the helm, install for very large scale deployments, and we are identifying areas of the helm chart that could be problematic in those large scale deployments as we're working on the migration.

A

So we will continue throughout the entire migration process to prioritize any of those issues that get identified and we do have some of those issues scheduled for 13.4.

A

Thank you so much for joining. I look forward to to talking to you next.

A