GitLab Configure Stage, 28 Jul 2021

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Deployment Direction Overview

Description

This video is a walkthrough of the highlights of the deployment direction and explains why a separate direction page for deployment was created.

https://about.gitlab.com/direction/deployment/

A

Hello, my name is kevin chu, I'm the group product manager for configure, release and monitor in this video. I want to walk you through the highlights of the deployment direction page. I also want to share with you some of the context behind why we felt a need to create a separate direction page in the first place, and this deployment page is somewhat unique in the sense that it's not tied to a specific stage.

A

Let me share my screen, so what is deployment we've defined deployment as the time when a developer promotes a coded, integrated and built software application to a production environment? Only after you deploy an application, can your users derive value from it? It is extremely important moment for that software application.

A

It is a point where all the development related efforts can start to pay off. As such, it is also viewed as a risky activity. After all, many of us have experienced deployments. That's gone wrong in some way.

A

Historically, gillab has treated deployment simply as the second part of cicd. Today developers can deploy their software by configuring, their prop project pipelines. In the same way, you implement continuous integration, namely, that is to set it up via the gitlab ci yaml file.

A

However, there's both a market recognition as well as a recognition internally at gitlab, that deployment is actually all together a different job. That's separate from continuous integration.

A

This job becomes even harder with the convergence with of applications and infrastructure merging via containerization, and it has actually always been difficult to do when it is scaled across a large organization.

A

For these reasons, we want to highlight this problem to solve and organize ourselves accordingly to solve this problem efficiently, and the first piece of this puzzle is to define a crisp vision and strategy, and we hope that we have done that via this direction page.

A

What is our vision? Our vision for deployment is to enable your organization to be an elite performer in devops by making the hardest part of devops deployment easy, flexible and secure. We recognize that organizations now often set up platforms with development teams or devop teams to create internal deployment platforms. We wanted to target that persona platform. Engineered directly henceforth will refer to that persona as priyanka by empowering priyanka to define and automate devops practices that has security and compliances guardrails built directly into the process.

A

We believe that enables enables her to enable her developers to own their specific deployment operations without toil, yet they get to retain the flexibility and efficiency gain from using priyanka's deployment platform.

A

We recognize that there's actually not just a single kind of deployment, the type of deployment targets and the scale of complexity by which the organization operates at creates different kinds of deployment challenges.

A

To accomplish our vision, we actually need to enable organizations to be good at deployment, no matter the type of deployment they're dealing with for independent deployments. These are deployments of individual projects that can be deployed in an automated fashion.

A

Users of gitlab today can leverage the cicd pipeline to achieve continuous deployment for deployments to kubernetes we're improving our ability to do so using the gitlab kubernetes agent and lastly, for orchestrated deployments.

A

These are complex deployments that require orchestration across multiple projects. We need to enable users to sequence: visualize, coordinate approvals, enable progressive delivery practices in order for these organizations to become the top devops performer scrolling down to our one year plan. What we're focused on now is to beef up our offerings specifically for kubernetes deployment and orchestrated deployments.

A

To do so we're going to create two new categories: first: environment: we want to enable priyanka to have a centralized view and get lab to coordinate all the deployments across her organizations and platform management. We want to give her a way to manage shared processes and resources, while simultaneously supporting team autonomy.

A

We also plan to continue to make improvements in kubernetes management, namely the kubernetes agent release, orchestration infrastructure as code and the ability to measure successful organizations. Thank you for watching this overview. If you have any questions, please follow the instructions. At the top of the page, to reach out to me directly cheers.