Learn how to use Jenkins X to automate your pipeline and achieve CI/CD.

DevOps for Developers

Jenkins X is a powerful tool for providing software developers continuous integration, automated testing, and continuous delivery, known as CI/CD, in Kubernetes.

It’s no secret that Kubernetes is extremely complex, and Jenkins X helps you by simplifying processes into concepts that can be adopted quickly and without spending months trying to figure out “the right way to do stuff.”

In this course, you’ll start by exploring the inner workings of Jenkins X and how to create a cluster using it. You’ll then learn how to combine Jenkins X with tools you’re already using. Throughout, you’ll see how this exciting new tool changes how you work with Kubernetes.

By the time you’re done, you will be confident managing CI/CD using Jenkins X in a Kubernetes cluster.

Jenkins X with Kubernetes

We dived into quite a few deployment strategies. Hopefully, you saw both the benefits and the limitations of each. You should be able to make a decision on which route to take. 

Parts of this chapter might have been overwhelming if you do not have practical knowledge of the technologies we used. That is especially true for **Istio**. Unfortunately, we could not dive into it in more detail since that would derail us from Jenkins X. **Knative**, **Istio**, and others each deserve a book or a series of articles themselves.

> 🔍 If you are eager to learn more about **Istio**, **Flagger**, and **Prometheus** in the context of canary deployments, you might want to explore the [Canary Deployments To Kubernetes Using Istio and Friends](https://www.udemy.com/course/canary-deployments-to-kubernetes-using-istio-and-friends/?referralCode=75549ECDBC41B27D94C4) course in Udemy. Occasionally, I will be posting coupons with discounts on my [Twitter](https://twitter.com/vfarcic) and [LinkedIn](https://www.linkedin.com/in/viktorfarcic/) accounts, so you might want to subscribe to one of those (if you're not already).

That's it. That was a long chapter, and you deserve a break.
# How to free up the resources?
If you created a cluster only for the exercises we executed, please destroy it. We'll start the next, and each other chapter from scratch as a way to save you from running your cluster longer than necessary and pay more than needed to your hosting vendor. If you created the cluster or installed Jenkins X using one of the Gists from the beginning of this chapter, you'll find the instructions on how to destroy the cluster or uninstall everything at the bottom of those Gists.

If you did choose to destroy the cluster or to uninstall Jenkins X, please remove the repositories we created as well as the local files. You can use the commands that follow for that. Just remember to replace `[...]` with your GitHub user and pay attention to the comments.



This lesson contains the instructions to free up the used resources. 

What Now?