Continuous Deployment to Kubernetes
Continuously deploying applications with Jenkins to a Kubernetes cluster
Kubernetes adoption has grown in leaps and bounds, over the past few months and it's the most popular container orchestration tool available. Led by expert, Victor Farcic, this course will help you start using Kubernetes to build a solid deployment pipeline. You'll work with the Kube API and you'll understand why continuous deployment should begin with shell scripts, rather than jumping into Jenkins. Once you're confident of packaging and distributing your applications, you'll set up Jenkins and create an automated continuous delivery pipeline. This course will give you some tools and knowledge to help you create a fully autonomous and automated continuous deployment pipeline.
What you'll learn-and how you can apply it
- Build a solid continuous delivery pipeline using Kubernetes, Jenkins, Helm and other tools
- Discover new features such as auto scaling, rolling updates, resource quotas, and cluster size
- Master the art of reliably rolling out new software versions without downtime or errors
This training course is for you because...
This course is for administrators and DevOps professionals who are eager to learn how to create autonomous CD pipelines using Kubernetes. You want to automate your release process by applying continuous delivery or deployment principles. You already have at least basic understanding how Kubernetes works and you want to leverage that to create a fully automated deployment pipeline using Jenkins.
Proficient with Deployments, ReplicaSets, Pods, Ingress, Services, PersistentVolumes, PersistentVolumeClaims, Namespaces and a few other things. Certain level of Kubernetes knowledge and hands-on experience is needed. If that's not the case, what follows might be too confusing and advanced. If you’d still like to participate, please read The DevOps 2.3 Toolkit: Kubernetes (https://amzn.to/2GvzDjy) first, or consult the Kubernetes documentation before you attend.
A fully operational Kubernetes cluster with NGINX Ingress controller and a default StorageClass. The following Kubernetes platforms were tested for this course. Please note that Gists are provided in case you need to create a cluster specific for this course.
- devops24-docker.sh: Docker for Mac with 4 CPUs, 4GB RAM, and with nginx Ingress controller.
- devops24-minikube.sh: minikube with 4 CPUs, 4GB RAM, and with ingress, storage-provisioner, and default-storageclass addons enabled.
- devops24-kops.sh: kops in AWS with 3 t2.medium masters and 3 t2.medium nodes spread in three availability zones, and with nginx Ingress controller.
- devops24-eks.sh: Elastic Kubernetes Service (EKS) with 3 t2.medium nodes, and with nginx Ingress controller.
- gke.sh: Google Kubernetes Engine (GKE) with 3 n1-standard-1 (1 CPU, 3.75GB RAM) nodes (one in each zone), with Cluster Autoscaler, and with nginx Ingress controller running on top of the "standard" one that comes with GKE.
If you are a Windows user, please use GitBash as a terminal for running the commands.
If you are running a local Kubernetes cluster with Docker For Mac/Windows, please install Vagrant (if you do not have it already).
Besides the cluster, you’ll need kubectl.
About your instructor
Viktor published The DevOps 2.0 Toolkit: Automating the Continuous Deployment Pipeline with Containerized Microservices, The DevOps 2.1 Toolkit: Docker Swarm: Building, testing, deploying, and monitoring services inside Docker Swarm clusters, The DevOps 2.2 Toolkit: Self-Sufficient Docker Clusters, and the Test-Driven Java Development by Packt Publishing.
Viktor's random thoughts and tutorials can be found in his blog TechnologyConversations.com.
The timeframes are only estimates and may vary according to how the class is progressing
Enabling Process Communication With Kube API Through Service Accounts - 45 mins
Humans are not the only ones who rely on a cluster. Processes in containers often need to invoke Kube API as well. When using RBAC for authentication, we need to decide which users will have permissions to perform specific actions. The same holds true for the processes running inside containers.
Defining Continuous Deployment – 90 mins
The work on defining Continuous Deployment (CDP) steps should not start in Jenkins or any other similar tool. Instead, we should focus on Shell commands and scripts and turn our attention to the CI/CD tools only once we are confident that we can execute the full process with only a few commands.
Break –~15 mins
Packaging Kubernetes Applications – 90 mins
Using YAML files to install or upgrade applications in a Kubernetes cluster works well only for static definitions. The moment we need to change an aspect of an application we are bound to discover the need for templating and packaging mechanisms.
Distributing Kubernetes Applications – 90 mins
Being able to package applications is of no use unless we can distribute them. A Kubernetes application is a combination of one or more container images and YAML files that describe them. If we are to distribute our applications, we need to store both container images and YAML definitions in repositories.
Installing and Setting Up Jenkins – 45 mins
When used by engineers, UIs are evil. They sidetrack us from repeatability and automation. We’ll try to fully automate Jenkins setup through a single CLI command.
Break ~ 45 mins
Creating A Continuous Deployment Pipeline With Jenkins – 90 mins
Having A Continuous Deployment pipeline capable of the fully automated application life-cycle is a true sign of maturity of an organization. We’ll do our best to create a pipeline that works without any manual (human) involvement.