Kubernetes is a powerful tool. It can help you manage complex applications and provide you with the ability to easily automate tasks involved in managing them. In this course, we will start exploring Kubernetes from a beginner's standpoint. We will discuss what Kubernetes is and what it does, and we will work with some of the basic functionality of Kubernetes hands-on. We will build a simple Kubernetes cluster. We will also deploy a sample microservice application to the cluster in order to explore how Kubernetes can help easily manage such applications.

A Practical Guide to Kubernetes

# Creating Jenkins Objects

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

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

kubectl rollout status deploy jenkins

We created an Ingress, a Deployment, and a Service object. We also executed the `kubectl rollout status` command that will tell us when the deployment is finished.

The `secret/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.

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) 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) secured by default.
# The Built-In Secrets

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

In this lesson, we will go through the built-in Kubernetes Secrets.

Exploring Built-In Secrets

Creating Jenkins Objects