1. Terraform Vs Kubernetes Infrastructure as Code (Iac) is built on immutable infrastructure: it uses orchestration tools to turn infrastructure into text, so you can manage infrastructure the way you manage code. In 2018 I was working on SaaS development, deploying on the Kubernetes platform, and that was the year Terraform was very hot.

1. Introduction to Jenkins X Relying on its massive plugin ecosystem, Jenkins currently holds most of the enterprise CICD engine market share. But in the cloud native era, Jenkins has also exposed many problems: a single point of service, disk storage, memory usage, and so on. Around Kubernetes, Jenkins X offers a DevOps approach better suited to the cloud native era.

In the previous document, we took advantage of the elasticity Kubernetes provides to dynamically create Jenkins Slaves on Kubernetes. This document is mainly a stress test of Jenkins under large-scale builds. 1. Cluster Configuration 1.1 Kubernetes Version The version used here is v1.16.7 1 2 3 4 kubectl version Client Version: version.

Author: (Russia) Oleg Skrynnik Publisher: Tsinghua University Press Publication year: 2020-05-01 ISBN: 9787302547143 Notes: As the title suggests, the book focuses on DevOps from a business perspective. From its origins to its foundations, from principles to practice, you can take something away at every level. DevOps rests on lean production (the Toyota production line) and agile development, with the value chain at its core.

Using Jenkins always means dealing with all kinds of plugins. To practice DevOps better, we should also be capable of developing plugins ourselves, so the whole process can converge inside Jenkins. 1. Jenkins Plugins 1.1 The Plugin Ecosystem Jenkins’ predecessor Hudson started in 2004, and 16 years on it is still a mainstream CI/CD engine.