In software engineering, continuous integration (CI) (https://en.wikipedia.org/wiki/Continuous_integration) and continuous delivery (CD) (https://en.wikipedia.org/wiki/Continuous_delivery), abbreviated as CI/CD, have the ability to simplify the procedure of the traditional development process with continuous developing, testing, and delivering mechanisms in order to reduce the panic of serious conflict, namely, to deliver small changes one at a time and to narrow down the problems immediately, if any. Furthermore, through automatic tools, a product delivered by the CI/CD system can achieve better efficiency and shorten time-to-market.

Jenkins is one of the well-known CI systems, which can be configured as a continuous delivery system. Jenkins can pull your project codes from the source code control system, run the tests, and then deploy based on your configuration. In this recipe, we will show you how to integrate Jenkins to Kubernetes to achieve continuous delivery.