Every so often in the Tech world there exists some conflict. Usually it’s great for customers and usually it steps from an article or impact statement from a group or company declaring something to be true. It’s always important to see multiple views when these occur. It’s also important to take it from a non-biased and clear view. Because there’s a lot of nuance. While one group may be technically accurate, the core of the statement made might still be largely true.
All Post by Christopher Timberlake
This is an article I’ve been meaning to write for a while. The purpose of this article is to cover the methodology and purpose behind “Purpose Built Containers”. This is a concept you’ve likely seen expressed elsewhere and in other canontations. As good example of this is the 12 Factor Application or OpenShift’s S2I. To be clear, these are not new concepts when it comes to containers, but it’s a methodology tied to GitLab and one that stands on the shoulders of giants.
By default GitLab & it’s Runners require anyuid and root access to work. They also require Helm charts to install. If you’re an OpenShift Administrator, these two things are likely not compatible with your way of doing things. You likely also dont want GitLab Runners to run CI Jobs using AnyUID and Root access. The purpose of this guide is to walk you through how to build your own GitLab Runner container that does not use Root or AnyUID. So that it’s secure and also communicated properly with GitLab.
In a previous article we wrote about how to use an external bot to obtain approvals. This method is one take on that problem. It has it’s advantages, such as having the bot being able to be tied into third party services. It can handle logging, it can collect information at approval time to pass to the pipeline. There’s alot of flexibility there. The downside being that it’s an external bot, and everything that comes with that.
Many companies and organizations that deal with IT have some form of Self-Service. Whether this be using something like ServiceNow, Microsoft Sharepoint, or something random like a Rube Goldberg Machine initiated by an e-mail. In either case, they have a system where users can go to a form, initiate a request and have a process ran. This functionality is a key requirement of process control theory. Today we’re going to discuss how we can use GitLab to handle Self-Service.