Safer Jenkins pipelines on kubernetes

Mon, 20 Apr 2020 12:45:04 +0200

Jenkins and kubernetes are a great combination. I love the concept of leveraing container technology to provide any build tools that you might require. However in many cases the examples provided are not always the best or most secure.

In Section 10.2.2 Building your image of Mannings Microservices in Action the following Jenkins Pipeline script is suggested:

def withPod(body) {
 podTemplate(label: 'pod', serviceAccount: 'jenkins', containers: [
 containerTemplate(name: 'docker', image: 'docker', command: 'cat', ttyEnabled: true),
 containerTemplate(name: 'kubectl', image: 'morganjbruce/kubectl', command: 'cat', ttyEnabled: true)
 ],
 volumes: [
 hostPathVolume(mountPath: '/var/run/docker.sock', hostPath: '/var/run/docker.sock'),
 ]
 ) { body() }
}

withPod {
 node('pod') {
 def tag = "${env.BRANCH_NAME}.${env.BUILD_NUMBER}"
 def service = "market-data:${tag}"
 checkout scm
 container('docker') {
 stage('Build') {
 sh("docker build -t ${service} .")
 }
 }
 container('kubectl') {
 stage('Deploy') {
 sh("kubectl --namespace=staging apply -f deploy/staging/")
 }
 }
 }
}

In this script there are three things that bother me:

Automated Kubernetes installation on Hyper-V

Fri, 10 Apr 2020 12:45:04 +0200

This artice describes how you can create a kubernetes custer using Vagrant, Hyper-V and Packer.

Update (11-05-2020)

I have updated the scripts to use contianerd in favor of docker. Don’t worry using docker is still possible. In /packer/ubuntu-18.04-amd64.json replace containerd.sh woth docker.sh.

Why?

I found myself in the need of having a kubernetes test cluster. Instead of using minikube or enabling Kubernetes on Docker Desktop. I thought I could learn from setting up a cluster from scratch. This also allows me to easiliy simulate network failures or have nodes go down.

Kubernetes on .NET wat we zoeken

Safer Jenkins pipelines on kubernetes

Automated Kubernetes installation on Hyper-V

Update (11-05-2020)

Why?