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

Servers are not involved in serverless computing.

Servers are not involved in serverless computing.

The task of creating and maintaining servers was removed with the emergence of cloud computing.

The task of creating and maintaining servers was removed with the emergence of cloud computing.

We can say that any application that can be packaged into a container image can run as a serverless deployment in Kubernetes.

We can say that any application that can be packaged into a container image can run as a serverless deployment in Kubernetes.

Which of the following are drawback of traditional Jenkins? (Multiple correct options)


Which of the following are drawback of traditional Jenkins? (Multiple correct options)

creating pipeline runs (a special type of Pods) when needed and destroying them when finished.

delivering  components used to build and run serverless applications on Kubernetes.

Tekton is incharge of _____________________________.

Tekton is incharge of _____________________________.

Using Knative’s scaling algorithm with default configurations, if we have 400 concurrent requests, then the system should scale to _______ replicas.

Using Knative’s scaling algorithm with default configurations, if we have 400 concurrent requests, then the system should scale to _______ replicas.

Preview environments have alot of downtime and having them scale to zero replicas when not in use saves significant resources. 

Preview environments are not same as production and can afford the slow boot-up time.

Why do we use serverless deployments with preview environments?

Why do we use serverless deployments with preview environments?

---
The next chapter will focus on the factors to consider while choosing the right deployment strategy.

Let's take a quiz and review some of the material we covered in this chapter. 

Quiz