U

Use kubernetes to test your build image in a Gitlab pipeline

When setting up a pipeline in Gitlab, the desired outcome for us is a tested and minimal docker image containing our application. Besides the problem how to build this image in the first place, there is another challenge: testing the image as a part of the pipeline, and only release it when all tests succeed. ...

K

Kaniko: how to build clean docker images in docker

Many people stumble upon the same problem as we did: you want an automated pipeline – but the result should always be a docker container. When utilizing kubernetes for running the stages of your pipeline, e.g. using Gitlab CI and its jobs, you will run into the problem that creating a container image requires a ...

Creating a Multi-Arch Kubernetes Cluster

During the last days and weeks, we focused on Kubernetes. It sounds like the most logical next step for evolving our CI/CD pipeline. And we knew before that Kubernetes is a different beast. It takes a while to get used to the concepts of Kubernetes, but that’s not even the hardest part. We figured out ...

Code to Container v4: the evolution of GitLab

As already introduced in the last Code to Container post, we’re moving to GitLab. We’ve started evaluating the Gitlab CI system first and now begin to move other parts such as the deployments to GitLab, too. This blog post is a bit shorter and mainly describes how we setup deployments using a manual build step ...

Code to Container v3: the discovery of GitLab

When I take another look at Code to Container v2 (our last sprint results), I get goose bumps 🙂 But that’s OK. In v2 we’ve created an pretty complex system of MQTT messaging and systems involving Continuous Integration (Circle CI, namely) and Continuous Deployment (self-made mqtt-triggered Docker deployers). When I look back and also taking ...

Browse Categories