Photo by Marek Piwnicki on Unsplash

Install MinIO in a Kubernetes cluster and use it as cache storage for your GitLab CI Runner. We’ll use Helm 3 to install both.

As mentioned in my article about setting up GitLab CI with MinIO using Helm 2, the default, one click installation from the GitLab admin panel is absolutely simple and works fine as long as you have no special requirement. Well, a cache for your CI jobs is not really a special requirement. However, setting it up can be more complicated you would expect.

Why MinIO? The GitLab Runner requires a cloud storage like Amazon S3 or…

When migrating an application from a monolithic approach to a microservices architecture, it’s not only a technical challenge but also requires a change in mindset for the development teams.

A monolith in nature. Photo by Zoltan Tasi on Unsplash

Monolith development

Ignoring the many mistakes one could do when designing a monolithic application, a benefit is, that usually the build and deployment is straight forward and the whole application needs not too many resources. Often a database and an application server are all you need to run the business logic and deliver for example a web user interface. …

Munich autumn sky

Setup a GitLab Runner in Kubernetes using MinIO for caching with the Helm 2 package manager.

Updated version for Helm 3 can be found here.

Connecting a Kubernetes cluster to GitLab is pretty simple. Even simpler, the installation of a GitLab Runner when you do it from the GitLab admin area in Kubernetes Applications. Install “Helm Tiller” (older GitLab versions) is one click and “GitLab Runner” the second. That works, but …

The so installed runner has a simple, default configuration and is not using any cache. …

Christof Aenderl

Passionate software developer and DevOps enthusiast

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store