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

# Kubernetes-based serverless computing
At this point, I must make an assumption that you, dear reader, might disagree with. Most companies will run at least some of their applications in Kubernetes. It is becoming a standard API that will be used by everyone. 

**Why is that assumption important?** If I'm right, then almost everyone will have a Kubernetes cluster. Everyone will spend time maintaining it, and everyone will have some level of in-house knowledge of how it works. If that assumption is correct, it stands to reason that Kubernetes would be the best choice for a platform to run serverless applications as well. As an added bonus, that would avoid vendor lock-in since Kubernetes can run almost anywhere.

**Kubernetes-based serverless computing** provides quite a few other benefits. 
- We are **free to write our applications in any language**, instead of being limited by those supported by function-as-a-service solutions offered through cloud vendors. 
- We **aren't limited to writing only functions**. 
- A **microservice or even a monolith** could run as a serverless application. We just need to find a solution to make that happen. After all, proprietary, cloud-specific, serverless solutions use containers as well. The standard mechanism for running containers is using Kubernetes.

There's an increasing number of Kubernetes platforms that allow us to run serverless applications. We won't go into all of those, but instead, fast-track the conversation by stating that **Knative** is likely going to become the de-facto standard in how to deploy serverless loads to Kubernetes. Maybe, it's already the most widely accepted standard by the time you read this.

This lesson states the benefits of Kubernetes-based serverless computing and also introduces Knative. 

Serverless Deployments in Kubernetes

Kubernetes-based serverless computing