Webserver With Live Rolling Updates Using Dynamic Jenkins Slave and Kubernetes

A Jenkins master can operate by itself both managing the build environment and executing the builds with its own executors and resources. If you stick with this “standalone” configuration you will most likely run out of resources when the number or the load of your projects increases.

The “jenkins” user that Jenkins uses to run the jobs would have full permissions on all Jenkins resources on the master, this will introduce a “security” issue while executing jobs on the master’s executors.

For these reasons, Jenkins has a master/slave mode where we can configure other Jenkins machines to be slave machines to take the load off the master Jenkins server.

This can be useful when we need several different environments to test our builds, in this scenario using a slave to represent each of your required environments is a good idea. Master and Slave communicate through TCP/IP protocol.

Here, I’ll launch a webserver using Kubernetes on Jenkins Dynamic Slave. I have also used the Kubernetes rolling update feature to update my webpage without any downtime.

First of all, we need to setup socket binding so as to allow the docker services of this VM to be used by others also. For this, we need to enable TCP support also. This is done by adding -H tcp://0.0.0.0:4243 in /usr/lib/systemd/system/docker.service file in the docker server.

Now restart your docker services using:

Now, a container image is created that has Linux and other basic configuration required to run Slave for Jenkins.

This image can be pulled from Docker Hub as well.

Related posts:

Building a marketplace website is a challenging process. To minimize the time and cost expenses, you should be prepared for the project development in advance. The main aspects you should consider…

Welcome to my second rapeh review. See my first review, on Yawanawa Warrior Princesse here. Cabolco Yopeiro is a potent variety of sacred Shamanic Snuff. I sourced this rapeh from rapee.shop, a…