Book Image

The DevOps 2.4 Toolkit

By : Viktor Farcic
Book Image

The DevOps 2.4 Toolkit

By: Viktor Farcic

Overview of this book

Building on The DevOps 2.3 Toolkit: Kubernetes, Viktor Farcic brings his latest exploration of the Docker technology as he records his journey to continuously deploying applications with Jenkins into a Kubernetes cluster. The DevOps 2.4 Toolkit: Continuously Deploying Applications with Jenkins to a Kubernetes Cluster is the latest book in Viktor Farcic’s series that helps you build a full DevOps Toolkit. This book guides readers through the process of building, testing, and deploying applications through fully automated pipelines. Within this book, Viktor will cover a wide-range of emerging topics, including an exploration of continuous delivery and deployment in Kubernetes using Jenkins. It also shows readers how to perform continuous integration inside these clusters, and discusses the distribution of Kubernetes applications, as well as installing and setting up Jenkins. Work with Viktor and dive into the creation of self-adaptive and self-healing systems within Docker.
Table of Contents (12 chapters)
Now It Is Your Turn

Deploying to production

We already saw that prod.yml is almost the same as build.yml we deployed earlier, so there's probably no need to go through it in details. The only substantial difference is that we'll create the resources in the go-demo-3 Namespace, and that we'll leave Ingress to its original path /demo.

 1  kubectl -n go-demo-3-build \
 2      exec -it cd -c kubectl -- sh
 4  cat k8s/prod.yml \
 5      | sed -e "s@:latest@:1.0@g" \
 6      | tee /tmp/prod.yml
 8  kubectl apply -f /tmp/prod.yml --record

We used sed to convert latest to the tag we built a short while ago, and we applied the definition. This was the first release, so all the resources were created.

Subsequent releases will follow the rolling update process. Since that is something Kubernetes does out-of-the-box, the command will always be the same.

Next, we'll wait until...