Brownfield

The new capability is running additional pods and services (and ingress and statefulsets) within the development namespace using the developer service account. This limited access role can’t impact other services but can start a container and use internal DNS and services to access them.

The GitLab Commit this summer is free for all with unlimited attendance due to the pandemic. This creates an opportunity for tons of people to have access to fantastic ideas that can help their organizations, teams, and individually.

In support of simplifying the Segregation of Duties pipeline definition, the Lab Assistant app will now create a dotenv formatted file and deliver it to the newly created branch. This perfectly meshes with what the Auto Deploy Image is expecting to allow Segregation of Auto DevOps Duties.

To help make it clear what the intermediate step is between the existing Deployment project example and real DevOps, I created a streamlined version.

The original recording was 40 minutes of chatting and pipelines and other nonsense. I sliced it up and we are left with about 9 minutes of the process and 4 minutes explaining a few pipeline jobs in greater detail.

When transitioning from classic methods to Agile and DevOps, the gatekeepers can feel stuck in limbo. The first step to easing the transition for security reviews, change management, and independent verification is to give them a place they control. As of GitLab 13-ish, the existing roles do not meet this need, despite the merge request approval with branch, tag, and environment protections.

This article lays out a 2 project workflow with an automated merge request handoff to support the access levels needed for segregation of duties with Auto DevOps.

Pushing the limits of mobility and performance has become easier now that the iPad Pro has the Magic Keyboard and Visual Studio Code can be web-based as code-server.

TL;DR: It’s pretty nice but has some shortcomings. This article covers both the workflow and configuration.

When multi-project workflows are necessary, the hand-offs can lead to repetition. To alleviate that, Lab Assistant will automate the hand-off for a multi-project workflows.

As DevOps evolves, new technologies enable better processes. If your team has a process defined by tradition, take a fresh look. Use some of these examples and keep an eye out for other accelerators as time passes.

Branches for input, merges for admission, tags for output.

GitLab released a dozen page book about Git Branching Strategies to serve as a high-level overview of branching strategies and how they work.

One of GitLab’s strengths is creating productivity-boosting constraints that positively impact system architecture and DevOps cycles. This is very clear in the Kubernetes-powered workflow, but discovering this can be impossible if an org is already locked into an ops-focused Kubernetes deployment.

Also, Kubernetes is entirely optional so don’t force it before the operations team is ready. Avoid ClickOps, even if that means delaying orchestration.