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

# Creating Jenkins objects

We'll create the same Jenkins objects we defined earlier. 

kubectl create \
    -f jenkins-unprotected.yml \
    --record --save-config

kubectl rollout status deploy jenkins

We create Ingress, Deployment, and Service objects. We also execute the `kubectl rollout status` command that will tell us when the deployment is finished, which  may take some time.

The `jenkins-unprotected.yml` definition does not use any new feature, so we won’t waste time going through the YAML file. Instead, we’ll open Jenkins UI in a browser.

kubectl port-forward service/jenkins 3000:8080 --address 0.0.0.0 
#Open the link beside the run button in the playground below

Upon closer inspection, you'll notice that there is no login button. Jenkins is currently unprotected. The image does allow the option to define an initial administrative username and password. 

If the files /etc/secrets/jenkins-user and /etc/secrets/jenkins-pass are present, the init script will read them and use the content inside those files to define the username and the password.

Since we’re already familiar with ConfigMaps, we could use them to generate those files. However, since the user and the password should be better protected than other configuration entries, we’ll switch to Secrets.


If you're interested in details, please explore the [jenkins/Dockerfile](https://github.com/vfarcic/docker-flow-stacks/blob/master/jenkins/Dockerfile) section from the [vfarcic/docker-flow-stack](https://github.com/vfarcic/docker-flow-stacks) repository. The important part is that it expects `/etc/secrets/jenkins-user` and `/etc/secrets/jenkins-pass` files. If we can provide them in a relatively secure manner, our Jenkins will be (more) secure by default.
# The Built-in Secrets

We'll start by checking whether we already have some Secrets in the cluster:

We’ll create the same Jenkins objects that we defined earlier.

Exploring Built-In Secrets

Creating Jenkins objects