Jump right into Kubernetes development with career-focused lessons and hands-on practice.

DevOps for Developers

Kubernetes is a powerful container management tool that's taking the world by storm. This detailed course will help you master it.

In this course, you'll start with the fundamentals of Kubernetes and what the main components of a cluster look like. You'll then learn how to use those components to build, test, deploy, and upgrade applications, as well as how to achieve state persistence once your application is deployed. You'll also learn how to secure your deployments and manage resources, which are crucial DevOps skills.

By the time you're done, you'll have a firm grasp on what Kubernetes is, as well as the skills to deploy your own clusters and applications with confidence.

A Practical Guide to Kubernetes

# Opening Jenkins in a browser
Now that everything is up and running, we can open Jenkins UI in a browser.



> **Note:** Git Bash might not be able to use the `open` command. If that's the case, please replace the `open` command with `echo`. As a result, you'll get the full address that should be opened directly in your browser of choice.
# Creating a job
Please click the “Log in” link, type “jdoe” as the User, and “incognito” as the Password. When finished, click the “Log in” button.

Now that we are authenticated as the `jdoe` administrator, we can proceed and create a job. This will generate a state we can use to explore what happens when a stateful application fails.

Please click the “Create new jobs” link, type “my-job” as the item name, select “Pipeline” as the job type, and press the “OK” button.

You’ll be presented with the job configuration screen. There’s no need to do anything here since we are not, at the moment, interested in any specific Pipeline definition. It’s enough to click the “Save” button.


# Simulating and analyzing failure
Next, we’ll simulate a failure by terminating a `java` process running inside the Pod created by the `jenkins` Deployment. To do that, we need to find out the name of the Pod.

Understand failure of the Jenkins application due to a lack of handling the state persistence.

Analyzing Failure of the Stateful Application

Opening Jenkins in a browser

Creating a job