LFD259 Labs - V2019 01 14

LFD259
Kubernetes for
Developers
Version 2019-01-14
LFD259: Version 2019-01-14
© Copyright the Linux Foundation 2019. All rights reserved.

ii
© Copyright the Linux Foundation 2019. All rights reserved.
The training materials provided or developed by The Linux Foundation in connection with the training services are protected
by copyright and other intellectual property rights.
Open source code incorporated herein may have other copyright holders and is used pursuant to the applicable open source
license.
The training materials are provided for individual use by participants in the form in which they are provided. They may not be
copied, modified, distributed to non-participants or used to provide training to others without the prior written consent of The
Linux Foundation.
No part of this publication may be reproduced, photocopied, stored on a retrieval system, or transmitted without express prior
written consent.
Published by:
the Linux Foundation

https://www.linuxfoundation.org
No representations or warranties are made with respect to the contents or use of this material, and any express or implied
warranties of merchantability or fitness for any particular purpose or specifically disclaimed.
Although third-party application software packages may be referenced herein, this is for demonstration purposes only and
shall not constitute an endorsement of any of these software applications.
Linux is a registered trademark of Linus Torvalds. Other trademarks within this course material are the property of their
respective owners.
If there are any questions about proper and fair use of the material herein, please contact:
[email protected]
LFD259: V 2019-01-14 © Copyright the Linux Foundation 2019. All rights reserved.
Contents
2 Kubernetes Architecture 1
3 Build 15
4 Design 29
5 Deployment Configuration 37
6 Security 53
7 Exposing Applications 67
8 Troubleshooting 75
iii
iv CONTENTS
Chapter 2
Kubernetes Architecture
Exercise 2.1: Overview and Preliminaries

We will create a two-node Ubuntu 16.04 cluster. Using two nodes allows an understanding of some issues and configurations
found in a production environment. While 2 vCPU and 8G of memory allows for quick labs you could use much smaller VMs.
Other Linux distributions should work in a very similar manner, but have not been tested.
Very Important
Regardless of the platform used (VirtualBox, VMWare, AWS, GCE or even bare metal) please remember that security
software like SELinux, AppArmor, and firewall configurations can prevent the labs from working. While not something
to do in production consider disabling the firewall and security software.
GCE requires a new VPC to be created and a rule allowing all traffic to be included. The use of wireshark can be a
helpful place to start with troubleshooting network and connectivity issues if you’re unable to open all ports.
The kubeadm utility currently requires that swap be turned off on every node. The swapoff -a command will do this
until the next reboot, with various methods to disable swap persistently. Cloud providers typically deploy instances with
swap disabled.
Download shell scripts and YAML files

To assist with setting up your cluster please download the tarball of shell scripts and YAML files. The k8sMaster.sh
and k8sSecond.sh scripts deploy a Kubernetes cluster using kubeadm and use Project Calico for networking.
Should the file not be found you can always use a browser to investigate the parent directory.
student@ckad-1:~$ wget
https://training.linuxfoundation.org/cm/LFD259/lfd259-example-file.1-13-1.tar \
--user=LFtraining --password=Penguin2014
student@ckad-1:~$ tar -xvf lfd259-example-file.1-13-1.tar
<output_omitted>
Exercise 2.2: Deploy a New Cluster
1
2 CHAPTER 2. KUBERNETES ARCHITECTURE
Deploy a Master Node using Kubeadm
1. Review the script to install and begin the configuration of the master kubernetes server:
k8sMaster.sh
#!/bin/bash -x
## TxS 1-2019
## v1.13.1 CKAD
echo "This script is written to work with Ubuntu 16.04"
sleep 3
echo
echo "Disable swap until next reboot"
echo
sudo swapoff -a
echo "Update the local node"

sudo apt-get update && sudo apt-get upgrade -y
echo
echo "Install Docker"
sleep 3
sudo apt-get install -y docker.io

echo
echo "Install kubeadm and kubectl"
sleep 3
sudo sh -c
,→ "echo 'deb http://apt.kubernetes.io/ kubernetes-xenial main' >> /etc/apt/sources.list.d/kubernetes.list"
sudo sh -c "curl -s https://packages.cloud.google.com/apt/doc/apt-key.gpg | apt-key add -"
sudo apt-get update
sudo apt-get install -y kubeadm=1.13.1-00 kubelet=1.13.1-00 kubectl=1.13.1-00
echo
echo "Installed - now to get Calico Project network plugin"
## If you are going to use a different plugin you'll want

## to use a different IP address, found in that plugins
## readme file.
sleep 3
sudo kubeadm init --kubernetes-version 1.13.1 --pod-network-cidr 192.168.0.0/16
sleep 5
echo "Running the steps explained at the end of the init output for you"
mkdir -p $HOME/.kube
sleep 2
sudo cp -i /etc/kubernetes/admin.conf $HOME/.kube/config
sleep 2
3
sudo chown $(id -u):$(id -g) $HOME/.kube/config
echo "Download Calico plugin and RBAC YAML files and apply"
wget https://tinyurl.com/yb4xturm -O rbac-kdd.yaml
wget https://tinyurl.com/y8lvqc9g -O calico.yaml
kubectl apply -f rbac-kdd.yaml
kubectl apply -f calico.yaml
echo
echo
sleep 3
echo "You should see this node in the output below"
echo "It can take up to a mintue for node to show Ready status"
echo
kubectl get node
echo
echo
echo "Script finished. Move to the next step"
2. Run the script as an argument to the bash shell. You will need the kubeadm join command shown near the end of the
output when you add the worker/minion node in a future step. Use the tee command to save the output of the script, in
case you cannot scroll back to find the kubeadm join in the script output.
student@ckad-1:~$ bash lfd259/k8sMaster.sh |tee ~/master.out
<output_omitted>
Your Kubernetes master has initialized successfully!
To start using your cluster, you need to run the

following as a regular user:
mkdir -p $HOME/.kube
sudo cp -i /etc/kubernetes/admin.conf $HOME/.kube/config
sudo chown $(id -u):$(id -g) $HOME/.kube/config
You should now deploy a pod network to the cluster.

Run kubectl apply -f [podnetwork].yaml with one
of the options listed at:
https://kubernetes.io/docs/concepts/cluster-administration/addons/
You can now join any number of machines by running the

following on each node as root:
kubeadm join 10.128.0.3:6443 --token 69rdjq.2x20l2j9ncexy37b

--discovery-token-ca-cert-hash
sha256:72143e996ef78301191b9a42184124416aebcf0c7f363adf9208f9fa599079bd
<output_omitted>
+ kubectl get node

NAME STATUS ROLES AGE VERSION
ckad-1 NotReady master 18s v1.13.1
+ echo
+ echo 'Script finished. Move to the next step'
Script finished. Move to the next step
Deploy a Minion Node
3. Open a separate terminal into your second node. Having both terminal sessions allows you to monitor the status of the
cluster while adding the second node. Copy the k8sSecond.sh file to the second node. View the file. You should see
the same early steps as on the master system.
k8sSecond.sh
#!/bin/bash -x
## TxS 1-2019
## CKAD for 1.13.1
##
echo " This script is written to work with Ubuntu 16.04"
echo
sleep 3
echo " Disable swap until next reboot"
echo
sudo swapoff -a
echo " Update the local node"

sleep 2
sudo apt-get update && sudo apt-get upgrade -y
echo
sleep 2
echo " Install Docker"

sleep 3
sudo apt-get install -y docker.io
echo
echo " Install kubeadm and kubectl"
sleep 2
sudo sh -c
,→ "echo 'deb http://apt.kubernetes.io/ kubernetes-xenial main' >> /etc/apt/sources.list.d/kubernetes.list"
sudo sh -c "curl -s https://packages.cloud.google.com/apt/doc/apt-key.gpg | apt-key add -"
sudo apt-get update
sudo apt-get install -y kubeadm=1.13.1-00 kubelet=1.13.1-00 kubectl=1.13.1-00
echo
echo " Script finished. You now need the kubeadm join command"
echo " from the output on the master node"
echo
4. Run the script on the second node.

student@ckad-2:~$ bash lfd259/k8sSecond.sh
<output_omitted>
5. When the script is done the minion node is ready to join the cluster. The kubeadm join statement can be found near
the end of the kubeadm init output on the master node. It should also be in the file master.out as well. Your nodes
will use a different IP address and hashes than the example below. You’ll need to pre-pend sudo to run the script copied
from the master node.
5
student@ckad-2:~$ sudo kubeadm join --token 118c3e.83b49999dc5dc034 \

10.128.0.3:6443 --discovery-token-ca-cert-hash \
sha256:40aa946e3f53e38271bae24723866f56c86d77efb49aedeb8a70cc189bfe2e1d
<output_omitted>
Configure the Master Node
6. Return to the master node. We will configure command line completion and verify both nodes have been added to the
cluster. The first command will configure completion in the current shell. The second command will ensure future shells
have completion.
student@ckad-1:~$ source <(kubectl completion bash)
student@ckad-1:~$ echo "source <(kubectl completion bash)" >> ~/.bashrc
7. Verify that both nodes are part of the cluster. Until we remove taints the nodes may not reach Ready state.
student@ckad-1:~$ kubectl get node
ckad-1 NotReady master 4m11s v1.13.1
ckad-2 NotReady <none> 3m6s v1.13.1
8. We will use the kubectl command for the majority of work with Kubernetes. Review the help output to become familiar
with commands options and arguments.
student@ckad-1:~$ kubectl --help
kubectl controls the Kubernetes cluster manager.
Find more information at:

https://kubernetes.io/docs/reference/kubectl/overview/
Basic Commands (Beginner):

create Create a resource from a file or from stdin.
expose Take a replication controller, service,
deployment or pod and expose it as a new Kubernetes Service
run Run a particular image on the cluster
set Set specific features on objects
run-container Run a particular image on the cluster. This
command is deprecated, use "run" instead
Basic Commands (Intermediate):

<output_omitted>
9. With more than 40 arguments, you can explore each also using the --help option. Take a closer look at a few, starting
with taint for example.
student@ckad-1:~$ kubectl taint --help
Update the taints on one or more nodes.
* A taint consists of a key, value, and effect. As an argument

here, it is expressed as key=value:effect.
* The key must begin with a letter or number, and may contain
letters, numbers, hyphens, dots, and underscores, up to
253 characters.
* Optionally, the key can begin with a DNS subdomain prefix
and a single '/',
like example.com/my-app
<output_omitted>
10. By default the master node will not allow general containers to be deployed for security reasons. This is via a taint.
Only containers which tolerate this taint will be scheduled on this node. As we only have two nodes in our cluster
we will remove the taint, allowing containers to be deployed on both nodes. This is not typically done in a production
environment for security and resource contention reasons. The following command will remove the taint from all nodes,
so you should see one success and one not found error. The worker/minion node does not have the taint to begin
with. Note the minus sign at the end of the command, which removes the preceding value.
student@ckad-1:~$ kubectl describe nodes |grep -i Taint
Taints: node-role.kubernetes.io/master:NoSchedule
Taints: node.kubernetes.io/not-ready:NoSchedule
student@ckad-1:~$ kubectl taint nodes \
--all node-role.kubernetes.io/master-node/ckad-1 untainted
taint "node-role.kubernetes.io/master:" not found
11. Check that both nodes are without a Taint. If they both are without taint the nodes should now show as Ready. It may
take a minute or two for all pods to enter Ready state.
student@ckad-1:~$ kubectl describe nodes |grep -i taint
Taints: <none>
Taints: <none>
student@ckad-1:~$ kubectl get nodes
ckad-1 Ready master 6m1s v1.13.1
ckad-2 Ready <none> 5m31s v1.13.1
Exercise 2.3: Create a Basic Pod
1. The smallest unit we directly control with Kubernetes is the pod. We will create a pod by creating a minimal YAML
file. First we will get a list of current API objects and their APIGROUP. If value is not shown it may not exist, as with
SHORTNAMES. Note that pods does not declare an APIGROUP. At the moment this indicates it is part of the stable v1
group.
student@ckad-1:~$ kubectl api-resources
NAME SHORTNAMES APIGROUP NAMESPACED KIND
bindings true Binding
componentstatuses cs false ComponentStatus
configmaps cm true ConfigMap
endpoints ep true Endpoints
.....
pods po true Pod
....
2. Finding no declared APIGROUP we will use v1 to denote a stable object. With that information we will add the other three
required sections such as metadata, with a name, and spec which declares which Docker image to use and a name for
the container. We will create an eight line YAML file. White space and indentation matters. Don’t use Tabs. There is a
basic.yaml file available in the tarball, as well as basic-later.yaml which shows what the file will become and can
be helpful for figuring out indentation.
1 apiVersion: v1
2 kind: Pod
3 metadata:
4 name: basicpod
5 spec:
6 containers:
7 - name: webcont
8 image: nginx
[basic.yaml]
3. Create the new pod using the recently created YAML file.
7
student@ckad-1:~$ kubectl create -f basic.yaml

pod/basicpod created
4. Make sure the pod has been created then use the describe sub-command to view the details. Among other values in
the output you should be about to find the image and the container name.
student@ckad-1:~$ kubectl get pod
NAME READY STATUS RESTARTS AGE
basicpod 1/1 Running 0 23s
student@ckad-1:~$ kubectl describe pod basicpod
Name: basicpod
Namespace: default
Priority: 0
<output_omitted>
5. Shut down the pod and verify it is no longer running.

student@ckad-1:~$ kubectl delete pod basicpod
pod "basicpod" deleted
No resources found.
6. We will now configure the pod to expose port 80. This configuration does not interact with the container to determine
what port to open. We have to know what port the process inside the container is using, in this case port 80 as a web
server. Add two lines to the end of the file. Line up the indentation with the image declaration.
student@ckad-1:~$ vim basic.yaml
basic.yaml
1 apiVersion: v1
2 kind: Pod
3 metadata:
4 name: basicpod
5 spec:
6 containers:
7 - name: webcont
8 image: nginx
9 ports:
10 - containerPort: 80
7. Create the pod and verify it is running. Use the -o wide option to see the internal IP assigned to the pod, as well
as NOMINATED NODE, which is used by the scheduler and READINESS GATES which show if experimental features are
enabled. Using curl and the pods IP address you shoudl get the default nginx welcome web page.
student@ckad-1:~$ kubectl get pod -o wide
NAME READY STATUS RESTARTS AGE IP NODE
NOMINATED NODE READINESS GATES
basicpod 1/1 Running 0 9s 192.168.1.3 ckad-1
<none> <none>
student@ckad-1:~$ curl http://192.168.1.3
<!DOCTYPE html>
<html>
<head>
<title>Welcome to nginx!</title>
<output_omitted>

8. We will now create a simple service to expose the pod to other nodes and pods in the cluster. The service YAML will
have the same four sections as a pod, but different spec configuration and the addition of a selector. We will also add
a label to the pod and a selector to the service so it knows which object to communicate with.
student@ckad-1:~$ vim basicservice.yaml
basicservice.yaml
1 apiVersion: v1
2 kind: Service
3 metadata:
4 name: basicservice
5 spec:
6 selector:
7 type: webserver
8 ports:
9 - protocol: TCP
10 port: 80
basic.yaml
1 apiVersion: v1
2 kind: Pod
3 metadata:
4 name: basicpod
5 labels: #<-- Add this line
6 type: webserver #<-- and this line which matches selector
7 spec:
8 ....
9. Create the new pod and service. Verify both have been created.
student@ckad-1:~$ kubectl create -f basicservice.yaml
service/basicservice created
basicpod 1/1 Running 0 110s
student@ckad-1:~$ kubectl get svc
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
basicservice ClusterIP 10.96.112.50 <none> 80/TCP 14s
kubernetes ClusterIP 10.96.0.1 <none> 443/TCP 4h
10. Test access to the web server using the CLUSTER-IP for the basicservice.
<!DOCTYPE html>
<html>
<head>
9
<output_omitted>
11. We will now expose the service to outside the cluster as well. Delete the service, edit the file and add a type declaration.
student@ckad-1:~$ kubectl delete svc basicservice
service "basicservice" deleted
student@ckad-1:~$ vim basicservice.yaml
basicservice.yaml
1 apiVersion: v1
2 kind: Service
3 metadata:
4 name: basicservice
5 spec:
6 selector:
7 type: webserver
8 type: NodePort #<--Add this line
9 ports:
10 - protocol: TCP
11 port: 80
12. Create the service again. Note there is a different TYPE and CLUSTER-IP and also a high-numbered port.
student@ckad-1:~$ kubectl create -f basicservice.yaml
service/basicservice created
basicservice NodePort 10.100.139.155 <none> 80:31514/TCP 3s
13. Using the public IP address of the node and the high port you should be able to test access to the webserver. In the
example below the public IP is 35.238.3.83, yours will be different. The high port will also probably be different.
local$ curl http://35.238.3.83:31514
<!DOCTYPE html>
<html>
<head>
<style>
<output_omitted>
14. Shut down the pod to prepare for the next section.
Exercise 2.4: Multi-Container Pods
Using a single container per pod allows for the most granularity and decoupling. There are still some reasons to deploy
multiple containers, sometimes called composite containers, in a single pod. The secondary containers can handle
logging or enhance the primary, the sidecar concept, or acting as a proxy to the outside, the ambassador concept, or
modifying data to meet an external format such as an adapter. All three concepts are secondary containers to perform
a function the primary container does not.
1. We will add a second container to the pod to handle logging. Without going into details of how to use fluentd we will
add a logging container to the exiting pod, which would act as a sidecar. At this state we will just add the second
container and verify it is running. In the Deployment Configuration chapter we will continue to work on this pod by
adding persistent storage and configure fluentd via a configMap.
Edit the YAML file and add a fluentd container. The dash should line up with the previous container dash. At this point
a name and image should be enough to start the second container.
basic.yaml
1 ....
2 containers:
3 - name: webcont
4 image: nginx
5 ports:
7 - name: fdlogger
8 image: k8s.gcr.io/fluentd-gcp:1.30
2. Delete and create the pod again. The commands can be typed on a single line, separated by a semicolon. The backslash
is only used to fit on the page. This time you should see 2/2 under the READY column. You should also find information
on the fluentd container inside of the kubectl describe output.
student@ckad-1:~$ kubectl delete pod basicpod ; \
kubectl create -f basic.yaml
basicpod 2/2 Running 0 2m8s
student@ckad-1:~$ kubectl describe pod basicpod
Name: basicpod
Namespace: default
Priority: 0
PriorityClassName: <none>
<output_omitted>
3. For now shut down the pod. We will use it again in a future exercise.
Exercise 2.5: Create a Simple Deployment
Creating a pod does not take advantage of orchestration abilities of Kubernetes. We will now create a Deployment
which gives use scalability reliability and updates.
1. Now run a containerized webserver nginx. Use kubectl create to create a simple, single replica deployment running
the nginx web server. It will create a single pod as we did previously but with new controllers to ensure it runs as well as
other features.
student@ckad-1:~$ kubectl create deployment firstpod --image=nginx
deployment.apps/firstpod created
2. Verify the new deployment exists and the desired number of pods matches the current number. Using a comma, you
can request two resource types at once. The Tab key can be helpful. Type enough of the word to be unique and press
the Tab key, it should complete the word. The deployment should show a number 1 for each value, such that the desired
number of pods matches the up-to-date and running number. The pod should show zero restarts.
11
student@ckad-1:~$ kubectl get deployment,pod

NAME READY UP-TO-DATE AVAILABLE AGE
deployment.extensions/firstpod 1/1 1 1 2m42s

pod/firstpod-7d88d7b6cf-lrsbk 1/1 Running 0 2m42s
3. View the details of the deployment, then the pod. Work through the output slowly. Knowing what a healthy deployment
and looks like can be helpful when troubleshooting issues. Again the Tab key can be helpful when using long auto-
generated object names. You should be able to type firstpodTab and the name will complete when viewing the pod.
student@ckad-1:~$ kubectl describe deployment firstpod
Name: firstpod
Namespace: default
CreationTimestamp: Fri, 25 Jul 2018 16:46:57 +0000
Labels: run=firstpod
Annotations: deployment.kubernetes.io/revision=1
Selector: run=firstpod
Replicas: 1 desired | 1 updated | 1 total | 1 available....
StrategyType: RollingUpdate
MinReadySeconds: 0
<output_omitted>
student@ckad-1:~$ kubectl describe pod firstpod-6bb4574d94-rqk76

Name: firstpod-6bb4574d94-rqk76
Namespace: default
Priority: 0
PriorityClassName: <none>
Node: ckad-1/10.128.0.2
Start Time: Wed, 25 Jul 2018 06:13:18 +0000
Labels: pod-template-hash=2660130850
run=firstpod
Annotations: <none>
Status: Running
IP: 192.168.200.65
Controlled By: ReplicaSet/firstpod-6bb4574d94
<output_omitted>
4. Note that the resources are in the default namespace. Get a list of available namespaces.
student@ckad-1:~$ kubectl get namespaces
NAME STATUS AGE
default Active 20m
kube-public Active 20m
kube-system Active 20m
5. There are two other namespaces. Look at the pods in the kube-system namespace.
student@ckad-1:~$ kubectl get pod -n kube-system
calico-etcd-rvrpk 1/1 Running 1 20m
calico-kube-controllers-d554689d5-lm687 1/1 Running 1 20m
calico-node-2ck9g 2/2 Running 4 19m
calico-node-kkxvl 2/2 Running 3 20m
etcd-ckad-1 1/1 Running 1 20m
<output_omitted>
6. Now look at the pods in a namespace that does not exist. Note you do not receive an error.
student@ckad-1:~$ kubectl get pod -n fakenamespace
No resources found.
7. You can also view resources in all namespaces at once. Use the --all-namespaces options to select objects in all
namespaces at once.
student@ckad-1:~$ kubectl get pod --all-namespaces
NAMESPACE NAME READY STATUS RESTARTS AGE
default firstpod-6bb4574d94-rqk76 1/1 Running 0 5m
kube-system calico-etcd-z49kx 1/1 Running 0 31m
kube-system calico-kube-controllers-d554689d5-pfszw 1/1 Running 0 31m
<output_omitted>
8. View several resources at once. Note that most resources have a short name such as rs for ReplicaSet, po for Pod,
svc for Service, and ep for endpoint.
student@ckad-1:~$ kubectl get deploy,rs,po,svc,ep
deployment.extensions/firstpod 1/1 1 1 4m
NAME DESIRED CURRENT READY....

replicaset.extensions/firstpod-6bb4574d94-rqk76 1 1 1 ....

pod/firstpod-6bb4574d94-rqk76 1/1 Running 0 4m

service/basicservice NodePort 10.108.147.76 <none> 80:31601/TCP 21m
service/kubernetes ClusterIP 10.96.0.1 <none> 443/TCP 21m
NAME ENDPOINTS AGE

endpoints/basicservice <none> 21m
endpoints/kubernetes 10.128.0.3:6443 21m
9. Delete the ReplicaSet and view the resources again. Note that the age on the ReplicaSet and the pod it controls is
now less than a minute. The deployment controller started a new ReplicaSet when we deleted the existing one, which
started another pod when the desired configuration did not match the current status.
student@ckad-1:~$ kubectl delete rs firstpod-6bb4574d94-rqk76
replicaset.extensions "firstpod-6bb4574d94-rqk76" deleted
student@ckad-1:~$ kubectl get deployment,rs,po,svc,ep

deployment.extensions/firstpod 1/1 1 1 7m
NAME DESIRED CURRENT....

replicaset.extensions/firstpod-6bb4574d94-rqk76 1 1 ....

pod/firstpod-7d99ffc75-p9hbw 1/1 Running 0 12s

service/kubernetes ClusterIP 10.96.0.1 <none> 443/TCP 24m
NAME ENDPOINTS AGE

endpoints/kubernetes 10.128.0.2:6443 80m
endpoints/basicservice <none> 21m
10. This time delete the top-level controller. After about 30 seconds for everything to shut down you should only see the
cluster service and endpoint remain for the cluster and the service we created.
student@ckad-1:~$ kubectl delete deployment firstpod
deployment.extensions "firstpod" deleted
student@ckad-1:~$ kubectl get deployment,rs,po,svc,ep
service/basicservice NodePort 10.108.147.76 <none> 80:31601/TCP 35m
13
kubernetes ClusterIP 10.96.0.1 <none> 443/TCP 24m
NAME ENDPOINTS AGE

kubernetes 10.128.0.3:6443 24m
11. As we won’t need it for a while, delete the basicservice service as well.
student@ckad-1:~$ kubectl delete svc basicservice
service "basicservice" deleted
Chapter 3
Build
Exercise 3.1: Deploy a New Application
Overview
In this lab we will deploy a very simple Python application, test it using Docker, ingest it into Kubernetes and con-
figure probes to ensure it continues to run. This lab requires the completion of the previous lab, the installation and
configuration of a Kubernetes cluster.
Working with Python
1. Install python on your master node. It may already be installed, as is shown in the output below.
student@ckad-1:~$ sudo apt-get -y install python
Reading package lists... Done
Building dependency tree
Reading state information... Done
python is already the newest version (2.7.12-1~16.04).
python set to manually installed.
0 upgraded, 0 newly installed, 0 to remove and 5 not upgraded.
student@ckad-1:~$
2. Locate the python binary on your system.

student@ckad-1:~$ which python
/usr/bin/python
3. Create and change into a new directory. The Docker build process pulls everything from the current directory into the
image file by default. Make sure the chosen directory is empty.
student@ckad-1:~$ mkdir app1
student@ckad-1:~$ cd app1
student@ckad-1:~/app1$ ls -l
total 0
4. Create a simple python script which prints the time and hostname every 5 seconds. There are six commented parts to
this script, which should explain what each part is meant to do. The script is included with others in the course tar file,
though you are encouraged to create the file by hand if not already familiar with the process.
15
16 CHAPTER 3. BUILD
simple.py
1 #!/usr/bin/python
2 ## Import the necessary modules
3 import time
4 import socket
5
6 ## Use an ongoing while loop to generate output

7 while True :
8
9 ## Set the hostname and the current date

10 host = socket.gethostname()
11 date = time.strftime( "%Y-%m- %d %H:%M:%S" )
12
13 ## Convert the date output to a string

14 now = str(date)
15
16 ## Open the file named date in append mode

17 ## Append the output of hostname and time
18 f = open( "date.out" , "a" )
19 f.write(now + " \n " )
20 f.write(host + " \n " )
21 f.close()
22
23 ## Sleep for five seconds then continue the loop

24 time.sleep(5)
5. Make the file executable and test that it works. Use Ctrl-C to interrupt the while loop after 20 or 30 seconds. The output
will be sent to a newly created file in your current directory called date.out.
student@ckad-1:~/app1$ chmod +x simple.py
student@ckad-1:~/app1$ ./simple.py
^CTraceback (most recent call last):
File "./simple.py", line 42, in <module>
time.sleep(5)
KeyboardInterrupt
6. and timedate stamps.

student@ckad-1:~/app1$ cat date.out
2018-03-22 15:51:38
ckad-1
2018-03-22 15:51:43
ckad-1
2018-03-22 15:51:48
ckad-1
<output_omitted>
7. Create a a file named Dockerfile.
Very Important
The name is important: it cannot have a suffix.
We will use three statements, FROM to declare which version of Python to use, ADD to include our script and CMD to
indicate the action of the container. Should you be including more complex tasks you may need to install extra libraries,
shown commented out as RUN pip install in the following example.
17
Dockerfile
FROM python:2
ADD simple.py /
## RUN pip install pystrich
CMD [ "python", "./simple.py" ]
8. Build the container. The output below shows mid-build as necessary software is downloaded. You will need to use sudo
in order to run this command. After the three step process completes the last line of output should indicate success.
student@ckad-1:~/app1$ sudo docker build -t simpleapp .
Sending build context to Docker daemon 3.072 kB
Step 1/3 : FROM python:2
2: Pulling from library/python
4176fe04cefe: Pull complete
851356ecf618: Pull complete
6115379c7b49: Pull complete
aaf7d781d601: Extracting [================> ] 54.03 MB/135 MB
40cf661a3cc4: Download complete
c582f0b73e63: Download complete
6c1ea8f72a0d: Download complete
7051a41ae6b7: Download complete
<output_omitted>
Successfully built c4e0679b9c36
9. Verify you can see the new image among others downloaded during the build process, installed to support the cluster,
or you may have already worked with. The newly created simpleapp image should be listed first.
student@ckad-1:~/app1$ sudo docker images
REPOSITORY TAG IMAGE ID CREATED SIZE
simpleapp latest c4e0679b9c36 2 minutes ago 681 MB
quay.io/calico/node v2.6.8 e96a297310fd 13 days ago 282 MB
python 2 d8690ef56706 2 weeks ago 681 MB
<output_omitted>
10. Use docker to run a container using the new image. While the script is running you won’t see any output and the shell
will be occupied running the image in the background. After 30 seconds use ctrl-c to interrupt. The local date.out file
will not be updated with new times, instead that output will be a file of the container image.
student@ckad-1:~$ sudo docker run simpleapp
^CTraceback (most recent call last):
File "./simple.py", line 24, in <module>
time.sleep(5)
KeyboardInterrupt
11. Locate the newly created date.out file. The following command should show two files of this name, the one created
when we ran simple.py and another under /var/lib/docker when run via a Docker container.
student@ckad-1:~/app1$ sudo find / -name date.out
/home/student/app1/date.out
/var/lib/docker/aufs/diff/ee814320c900bd24fad0c5db4a258d3c2b78a19cde
629d7de7d27270d6a0c1f5/date.out
12. View the contents of the date.out file created via Docker. Note the need for sudo as Docker created the file this time,
and the owner is root. The long name is shown on several lines in the example, but would be a single line when typed
or copied.
student@ckad-1:~/app1$ sudo tail \
/var/lib/docker/aufs/diff/ee814320c900bd24fad0c5db4a258d3c2b78a19cde629d7de7d27270d6a0c1f5/date.out
2018-03-22 16:13:46
53e1093e5d39
2018-03-22 16:13:51
18 CHAPTER 3. BUILD
53e1093e5d39
2018-03-22 16:13:56
53e1093e5d39
Exercise 3.2: Configure A Local Docker Repo
While we could create an account and upload our application to hub.docker.com, thus sharing it with the world, we
will instead create a local repository and make it available to the nodes of our cluster.
1. We’ll need to complete a few steps with special permissions, for ease of use we’ll become root using sudo.
student@ckad-1:~/app1$ cd
student@ckad-1:~$ sudo -i
2. Install the docker-compose software and utilities to work with the nginx server which will be deployed with the registry.
root@ckad-1:~# apt-get install -y docker-compose apache2-utils
<output_omitted>
3. Create a new directory for configuration information. We’ll be placing the repository in the root filesystem. A better
location may be chosen in a production environment.
root@ckad-1:~# mkdir -p /localdocker/data
root@ckad-1:~# cd /localdocker/
4. Create a Docker compose file. Inside is an entry for the nginx web server to handle outside traffic and a registry entry
listening to loopback port 5000 for running a local Docker registry.
docker-compose.yaml
1 nginx:
2 image: "nginx:1.12"
3 ports:
4 - 443:443
5 links:
6 - registry:registry
7 volumes:
8 - /localdocker/nginx/:/etc/nginx/conf.d
9 registry:
10 image: registry:2
11 ports:
12 - 127.0.0.1:5000:5000
13 environment:
14 REGISTRY_STORAGE_FILESYSTEM_ROOTDIRECTORY: /data
15 volumes:
16 - /localdocker/data:/data
5. Use the docker-compose up command to create the containers declared in the previous step YAML file. This will
capture the terminal and run until you use ctrl-c to interrupt. There should be five registry_1 entries with info messages
about memory and which port is being listened to. Once we’re sure the Docker file works we’ll convert to a Kubernetes
tool.
root@ckad-1:/localdocker# docker-compose up
Pulling nginx (nginx:1.12)...
1.12: Pulling from library/nginx
2a72cbf407d6: Pull complete
f37cbdc183b2: Pull complete
78b5ad0b466c: Pull complete
Digest: sha256:edad623fc7210111e8803b4359ba4854e101bcca1fe7f46bd1d35781f4034f0c
19
Status: Downloaded newer image for nginx:1.12

Creating localdocker_registry_1
Creating localdocker_nginx_1
Attaching to localdocker_registry_1, localdocker_nginx_1
registry_1 | time="2018-03-22T18:32:37Z" level=warning msg="No HTTP secret provided - generated ran
<output_omitted>
6. Test that you can access the repository. Open a second terminal to the master node. Use the curl command to test the
repository. It should return {}, but does not have a carriage-return so will be on the same line as the following prompt.
You should also see the GET request in the first, captured terminal, without error. Don’t forget the trailing slash. You’ll
see a “Moved Permanently” message if the path doesn’t match exactly.
student@ckad-1:~/localdocker$ curl http://127.0.0.1:5000/v2/
student@ckad-1:~/localdocker$
7. Now that we know docker-compose format is working, ingest the file into Kubernetes using kompose. Use ctrl-c to
stop the previous docker-compose command.
^CGracefully stopping... (press Ctrl+C again to force)
Stopping localdocker_nginx_1 ... done
Stopping localdocker_registry_1 ... done
8. Download the kompose binary and make it executable. The command can run on a single line. Note that the option
following the dash is the letter as in output.
root@ckad-1:/localdocker# curl -L \
https://github.com/kubernetes/kompose/releases/download/v1.1.0/kompose-linux-amd64 -o kompose
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 609 0 609 0 0 1963 0 --:--:-- --:--:-- --:--:-- 1970
100 45.3M 100 45.3M 0 0 16.3M 0 0:00:02 0:00:02 --:--:-- 25.9M
root@ckad-1:/localdocker# chmod +x kompose
9. Move the binary to a directory in our $PATH. Then return to your non-root user.
root@ckad-1:/localdocker# mv ./kompose /usr/local/bin/kompose
root@ckad-1:/localdocker# exit
10. Create two physical volumes in order to deploy a local registry for Kubernetes. 200Mi for each should be enough for
each of the volumes. Use the hostPath storageclass for the volumes.
More details on how persistent volumes and persistent volume claims are covered in an upcoming chapter.
vol1.yaml
1 apiVersion: v1
2 kind: PersistentVolume
3 metadata:
4 labels:
5 type: local
6 name: task-pv-volume
7 spec:
8 accessModes:
9 - ReadWriteOnce
10 capacity:
11 storage: 200Mi
12 hostPath:
13 path: /tmp/data
14 persistentVolumeReclaimPolicy: Retain
20 CHAPTER 3. BUILD
vol2.yaml
1 apiVersion: v1
3 metadata:
4 labels:
5 type: local
6 name: registryvm
7 spec:
8 accessModes:
9 - ReadWriteOnce
10 capacity:
11 storage: 200Mi
12 hostPath:
13 path: /tmp/nginx
11. Create both volumes.

student@ckad-1:~$ kubectl create -f vol1.yaml
persistentvolume/task-pv-volume created
student@ckad-1:~$ kubectl create -f vol2.yaml
persistentvolume/registryvm created
12. Verify both volumes have been created. They should show an Available status.
student@ckad-1:~$ kubectl get pv
NAME CAPACITY ACCESS MODES RECLAIM POLICY STATUS
CLAIM STORAGECLASS REASON AGE
registryvm 200Mi RWO Retain Available
27s
task-pv-volume 200Mi RWO Retain Available
32s
13. Go to the configuration file directory for the local Docker registry.
student@ckad-1:~$ cd /localdocker/
student@ckad-1:~/localdocker$ ls
data docker-compose.yaml nginx
14. Convert the Docker file into a single YAML file for use with Kubernetes. Not all objects convert exactly from Docker to
kompose, you may get errors about the mount syntax for the new volumes. They can be safely ignored.
student@ckad-1:~/localdocker$ sudo kompose convert -f docker-compose.yaml -o localregistry.yaml
WARN Volume mount on the host "/localdocker/nginx/" isn't supported - ignoring path on the host
WARN Volume mount on the host "/localdocker/data" isn't supported - ignoring path on the host
15. Review the file. You’ll find that multiple Kubernetes objects will have been created such as Services,
Persistent Volume Claims and Deployments using environmental parameters and volumes to configure the
container within.
student@ckad-1:/localdocker$ less localregistry.yaml
apiVersion: v1
items:
- apiVersion: v1
kind: Service
metadata:
annotations:
kompose.cmd: kompose convert -f docker-compose.yaml -o localregistry.yaml
kompose.version: 1.1.0 (36652f6)
creationTimestamp: null
labels:
21
<output_omitted>
16. View the cluster resources prior to deploying the registry. Only the cluster service and two available persistent volumes
should exist in the default namespace.
student@ckad-1:~/localdocker$ kubectl get pods,svc,pvc,pv,deploy
NAME CAPACITY ACCESS MODES RECLAIM POLICY

STATUS CLAIM STORAGECLASS REASON AGE
persistentvolume/registryvm 200Mi RWO Retain
Available 15s
persistentvolume/task-pv-volume 200Mi RWO Retain
Available 17s
17. Use kubectl to create the local docker registry.

student@ckad-1:~/localdocker$ kubectl create -f localregistry.yaml
service/nginx created
service/registry created
deployment.extensions/nginx created
persistentvolumeclaim/nginx-claim0 created
deployment.extensions/registry created
persistentvolumeclaim/registry-claim0 created
18. View the newly deployed resources. The persistent volumes should now show as Bound. Find the service IP for the
registry. It should be sharing port 5000. In the example below the IP address is 10.110.186.162, yours may be different.
student@ckad-1:~/localdocker$ kubectl get pods,svc,pvc,pv,deploy
pod/nginx-6b58d9cdfd-95zxq 1/1 Running 0 1m
pod/registry-795c6c8b8f-b8z4k 1/1 Running 0 1m

service/kubernetes ClusterIP 10.96.0.1 <none> 443/TCP 1h
service/nginx ClusterIP 10.106.82.218 <none> 443/TCP 1m
service/registry ClusterIP 10.110.186.162 <none> 5000/TCP 1m
NAME STATUS VOLUME

CAPACITY ACCESS MODES STORAGECLASS AGE
persistentvolumeclaim/nginx-claim0 Bound registryvm
200Mi RWO 1m
persistentvolumeclaim/registry-claim0 Bound task-pv-volume
200Mi RWO 1m

persistentvolume/registryvm 200Mi RWO Retain
Bound
default/nginx-claim0 5m
persistentvolume/task-pv-volume 200Mi RWO Retain
Bound
default/registry-claim0 6m

deployment.extensions/nginx 1/1 1 1 12s
deployment.extensions/registry 1/1 1 1 12s
19. Verify you get the same {} response using the Kubernetes deployed registry as we did when using docker-compose.
Note you must use the trailing slash after v2. Please also note that if the connection hangs it may be due to a firewall
issue. If running your nodes using GCE ensure your instances are using VPC setup and all ports are allowed. If using
AWS also make sure all ports are being allowed.
22 CHAPTER 3. BUILD
student@ckad-1:~/localdocker$ curl http://10.110.186.162:5000/v2/

student@ckad-1:~/localdocker$
20. Edit the Docker configuration file to allow insecure access to the registry. In a production environment steps should be
taken to create and use TLS authentication instead. Use the IP and port of the registry you verified in the previous step.
student@ckad-1:~$ sudo vim /etc/docker/daemon.json
"insecure-registries":["10.110.186.162:5000"]
21. Restart docker on the local system. It can take up to a minute for the restart to take place.
student@ckad-1:~$ sudo systemctl restart docker.service
22. Download and tag a typical image from hub.docker.com. Tag the image using the IP and port of the registry. We will
also use the latest tag.
student@ckad-1:~$ sudo docker pull ubuntu
Using default tag: latest
latest: Pulling from library/ubuntu
<output_omitted>
Digest: sha256:9ee3b83bcaa383e5e3b657f042f4034c92cdd50c03f73166c145c9ceaea9ba7c
Status: Downloaded newer image for ubuntu:latest
student@ckad-1:~$ sudo docker tag ubuntu:latest 10.110.186.162:5000/tagtest
23. Push the newly tagged image to your local registry. If you receive an error about an HTTP request to an HTTPS client
check that you edited the /etc/docker/daemon.json file correctly and restarted the service.
student@ckad-1:~$ sudo docker push 10.110.186.162:5000/tagtest
The push refers to a repository [10.110.186.162:5000/tagtest]
db584c622b50: Pushed
52a7ea2bb533: Pushed
52f389ea437e: Pushed
88888b9b1b5b: Pushed
a94e0d5a7c40: Pushed
latest: digest: sha256:0847cc7fed1bfafac713b0aa4ddfb8b9199a99092ae1fc4e718cb28e8528f65f size: 1357
24. We will test to make sure we can also pull images from our local repository. Begin by removing the local cached images.
student@ckad-1:~$ sudo docker image remove ubuntu:latest
Untagged: ubuntu:latest
Untagged: ubuntu@sha256:e348fbbea0e0a0e73ab0370de151e7800684445c509d46195aef73e090a49bd6
student@ckad-1:~$ sudo docker image remove 10.110.186.162:5000/tagtest
Untagged: 10.110.186.162:5000/tagtest:latest
<output_omitted>
25. Pull the image from the local registry. It should report the download of a newer image.
student@ckad-1:~$ sudo docker pull 10.110.186.162:5000/tagtest
latest: Pulling from tagtest
Digest: sha256:0847cc7fed1bfafac713b0aa4ddfb8b9199a99092ae1fc4e718cb28e8528f65f
Status: Downloaded newer image for 10.110.186.162:5000/tagtest:latest
26. Use docker tag to assign the simpleapp image and then push it to the local registry. The image and dependent images
should be pushed to the local repository.
student@ckad-1:~$ sudo docker tag simpleapp 10.110.186.162:5000/simpleapp
student@ckad-1:~$ sudo docker push 10.110.186.162:5000/simpleapp
The push refers to a repository [10.110.186.162:5000/simpleapp]
321938b97e7e: Pushed
ca82a2274c57: Pushed
de2fbb43bd2a: Pushed
4e32c2de91a6: Pushed
23
6e1b48dc2ccc: Pushed
ff57bdb79ac8: Pushed
6e5e20cbf4a7: Pushed
86985c679800: Pushed
8fad67424c4e: Pushed
latest: digest: sha256:67ea3e11570042e70cdcbad684a1e2986f59aaf53703e51725accdf5c70d475a size: 2218
27. Configure the worker (second) node to use the local registry running on the master server. Connect to the worker node.
Edit the Docker daemon.json file with the same values as the master node and restart the service.
student@ckad-2:~$ sudo vim /etc/docker/daemon.json
"insecure-registries":["10.110.186.162:5000"]
student@ckad-2:~$ sudo systemctl restart docker.service
28. Pull the recently pushed image from the registry running on the master node.
student@ckad-2:~$ sudo docker pull 10.110.186.162:5000/simpleapp
latest: Pulling from simpleapp
f65523718fc5: Pull complete
1d2dd88bf649: Pull complete
c09558828658: Pull complete
0e1d7c9e6c06: Pull complete
c6b6fe164861: Pull complete
45097146116f: Pull complete
f21f8abae4c4: Pull complete
1c39556edcd0: Pull complete
85c79f0780fa: Pull complete
Digest: sha256:67ea3e11570042e70cdcbad684a1e2986f59aaf53703e51725accdf5c70d475a
Status: Downloaded newer image for 10.110.186.162:5000/simpleapp:latest
29. Return to the master node and deploy the simpleapp in Kubernetes with several replicas. We will name the deployment
try1. Scale to have six replicas. Multiple replicas the scheduler should run some containers on each node.
student@ckad-1:~$ kubectl create deployment try1 --image=10.110.186.162:5000/simpleapp:latest
deployment.apps/try1 created
student@ckad-1:~$ kubectl scale deployment try1 --replicas=6
deployment.extensions/try1 scaled
30. View the running pods. You should see six replicas of simpleapp as well as two running the locally hosted image
repository.
student@ckad-1:~$ kubectl get pods
nginx-6b58d9cdfd-j6jm6 1/1 Running 1 13m
registry-795c6c8b8f-5jnpn 1/1 Running 1 13m
try1-857bdcd888-6klrr 1/1 Running 0 25s
try1-857bdcd888-9pwnp 1/1 Running 0 25s
try1-857bdcd888-9xkth 1/1 Running 0 25s
try1-857bdcd888-tw58z 1/1 Running 0 25s
try1-857bdcd888-xj9lk 1/1 Running 0 25s
try1-857bdcd888-znpm8 1/1 Running 0 25s
31. On the second node use sudo docker ps to verify containers of simpleapp are running. The scheduler will try to
deploy an equal number to both nodes by default.
student@ckad-2:~$ sudo docker ps | grep simple
3ae4668d71d8 \
10.110.186.162:5000/simpleapp@sha256:67ea3e11570042e70cdcbad684a1e2986f59aaf53703e51725accdf5c70d475a \
"python ./simple.py" 48 seconds ago Up 48 seconds \
k8s_try1_try1-857bdcd888-9xkth_default_2e94b97e-322a-11e8-af56-42010a800004_0
ef6448764625 \
10.110.186.162:5000/simpleapp@sha256:67ea3e11570042e70cdcbad684a1e2986f59aaf53703e51725accdf5c70d475a \
24 CHAPTER 3. BUILD
"python ./simple.py" 48 seconds ago Up 48 seconds \

k8s_try1_try1-857bdcd888-znpm8_default_2e99f356-322a-11e8-af56-42010a800004_0
32. Return to the master node. Save the try1 deployment as YAML. Use the –export option to remove unique identifying
information. The command is shown on two lines for readability. You can remove the backslash when you run the
command.
student@ckad-1:~/app1$ cd ~/app1/
student@ckad-1:~/app1$ kubectl get deployment try1 -o yaml --export > simpleapp.yaml
33. Double check that use of --export removed creationTimestamp, selfLink, uid, resourceVersion, and all the
Status information. In newer versions of Kubernetes it seems to no longer be necessary to remove these values in
order to deploy again. Be aware older versions would error if these values were found in the YAML file. For backwards
compatibility we will continue to remove these entries.
student@ckad-1:~/app1$ vim simpleapp.yaml
<output_omitted>
34. Delete and recreate the try1 deployment using the YAML file. Verify the deployment is running with the expected six
replicas.
student@ckad-1:~$ kubectl delete deployment try1
deployment.extensions "try1" deleted
student@ckad-1:~/app1$ kubectl create -f simpleapp.yaml
deployment.extensions/try1 created
student@ckad-1:~/app1$ kubectl get deployment
nginx 1/1 1 1 15m
registry 1/1 1 1 15m
try1 6/6 6 6 5s
Exercise 3.3: Configure Probes
When large datasets need to be loaded or a complex application launched prior to client access, a readinessProbe
can be used. The pod will not become available to the cluster until a test is met and returns a successful exit code.
Both readinessProbes and livenessProbes use the same syntax and are identical other than the name. Where the
readinessProbe is checked prior to being ready, then not again, the livenessProbe continues to be checked.
There are three types of liveness probes: a command returns a zero exit value, meaning success, an HTTP request
returns a response code in the 200 to 399 range, and the third probe uses a TCP socket. In this example we’ll use a
command, cat, which will return a zero exit code when the file /tmp/healthy has been created and can be accessed.
1. Edit the YAML deployment file and add the stanza for a readinessprobe. Remember that when working with YAML
whitespace matters. Indentation is used to parse where information should be associated within the stanza and the
entire file. Do not use tabs. If you get an error about validating data, check the indentation. It can also be helpful to
paste the file to this website to see how indentation affects the JSON value, which is actually what Kubernetes ingests:
https://www.json2yaml.com/
simpleapp.yaml
1 ....
2 spec:
3 containers:
4 - image: 10.111.235.60:5000/simpleapp:latest
5 imagePullPolicy: Always
25
6 name: simpleapp
7 readinessProbe:
8 exec:
9 command:
10 - cat
11 - /tmp/healthy
12 periodSeconds: 5
13 resources: {}
14 ....
2. Delete and recreate the try1 deployment.

student@ckad-1:~/app1$ kubectl delete deployment try1
student@ckad-1:~/app1$ kubectl create -f simpleapp.yaml
3. The new try1 deployment should reference six pods, but show zero available. They are all missing the /tmp/healthy
file.
student@ckad-1:~/app1$ kubectl get deployment
nginx 1/1 1 1 19m
registry 1/1 1 1 19m
try1 0/6 6 0 15s
4. Take a closer look at the pods. Choose one of the try1 pods as a test to create the health check file.
student@ckad-1:~/app1$ kubectl get pods
nginx-6b58d9cdfd-g7lnk 1/1 Running 1 40m
registry-795c6c8b8f-7vwdn 1/1 Running 1 40m
try1-9869bdb88-2wfnr 0/1 Running 0 26s
try1-9869bdb88-6bknl 0/1 Running 0 26s
try1-9869bdb88-786v8 0/1 Running 0 26s
try1-9869bdb88-gmvs4 0/1 Running 0 26s
try1-9869bdb88-lfvlx 0/1 Running 0 26s
try1-9869bdb88-rtchc 0/1 Running 0 26s
5. Run the bash shell interactively and touch the /tmp/healthy file.
student@ckad-1:~/app1$ kubectl exec -it try1-9869bdb88-rtchc -- /bin/bash
root@try1-9869bdb88-rtchc:/# touch /tmp/healthy
root@try1-9869bdb88-rtchc:/# exit
exit
6. Wait at least five seconds, then check the pods again. Once the probe runs again the container should show available
quickly. The pod with the existing /tmp/healthy file should be running and show 1/1 in a READY state. The rest will
continue to show 0/1.
nginx-6b58d9cdfd-g7lnk 1/1 Running 1 44m
registry-795c6c8b8f-7vwdn 1/1 Running 1 44m
try1-9869bdb88-2wfnr 0/1 Running 0 4m
try1-9869bdb88-6bknl 0/1 Running 0 4m
try1-9869bdb88-786v8 0/1 Running 0 4m
try1-9869bdb88-gmvs4 0/1 Running 0 4m
26 CHAPTER 3. BUILD
try1-9869bdb88-lfvlx 0/1 Running 0 4m

try1-9869bdb88-rtchc 1/1 Running 0 4m
7. Touch the file in the remaining pods. Consider using a for loop, as an easy method to update each pod. Note the
>shown in the output represents the secondary prompt, you would not type in that character
student@ckad-1:~$ for name in try1-9869bdb88-2wfnr try1-9869bdb88-6bknl \
> try1-9869bdb88-786v8 try1-9869bdb88-gmvs4 try1-9869bdb88-lfvlx
> do
> kubectl exec $name touch /tmp/healthy
> done
8. It may take a short while for the probes to check for the file and the health checks to succeed.
nginx-6b58d9cdfd-g7lnk 1/1 Running 1 1h
registry-795c6c8b8f-7vwdn 1/1 Running 1 1h
try1-9869bdb88-2wfnr 1/1 Running 0 22m
try1-9869bdb88-6bknl 1/1 Running 0 22m
try1-9869bdb88-786v8 1/1 Running 0 22m
try1-9869bdb88-gmvs4 1/1 Running 0 22m
try1-9869bdb88-lfvlx 1/1 Running 0 22m
try1-9869bdb88-rtchc 1/1 Running 0 22m
9. Now that we know when a pod is healthy, we may want to keep track that it stays healthy, using a livenessProbe. You
could use one probe to determine when a pod becomes available and a second probe, to a different location, to ensure
ongoing health.
Edit the deployment again. Add in a livenessProbe section as seen below. This time we will add a Sidecar container
to the pod running a simple application which will respond to port 8080. Note that the dash (-) in front of the name. Also
goproxy is indented the same number of spaces as the - in front of the image: line for simpleapp earlier in the file. In
this example that would be seven spaces
simpleapp.yaml
1 ....
2 terminationMessagePath: /dev/termination-log
3 terminationMessagePolicy: File
4 - name: goproxy
5 image: k8s.gcr.io/goproxy:0.1
6 ports:
8 readinessProbe:
9 tcpSocket:
10 port: 8080
11 initialDelaySeconds: 5
12 periodSeconds: 10
13 livenessProbe:
14 tcpSocket:
15 port: 8080
18 dnsPolicy: ClusterFirst
19 restartPolicy: Always
20 ....
10. Delete and recreate the deployment.

27
student@ckad-1:~$ kubectl create -f simpleapp.yaml

11. View the newly created pods. You’ll note that there are two containers per pod, and only one is running. The
new simpleapp containers will not have the /tmp/healthy file, so they will not become available until we touch the
/tmp/healthy file again. We could include a command which creates the file into the container arguments. The output
below shows it can take a bit for the old pods to terminate.
try1-76cc5ffcc6-4rjvh 1/2 Running 0 3s
try1-76cc5ffcc6-bk5f5 1/2 Running 0 3s
try1-76cc5ffcc6-d8n5q 0/2 ContainerCreating 0 3s
try1-76cc5ffcc6-mm6tw 1/2 Running 0 3s
try1-76cc5ffcc6-r9q5n 1/2 Running 0 3s
try1-76cc5ffcc6-tx4dz 1/2 Running 0 3s
try1-9869bdb88-2wfnr 1/1 Terminating 0 12h
try1-9869bdb88-6bknl 1/1 Terminating 0 12h
try1-9869bdb88-786v8 1/1 Terminating 0 12h
try1-9869bdb88-gmvs4 1/1 Terminating 0 12h
try1-9869bdb88-lfvlx 1/1 Terminating 0 12h
try1-9869bdb88-rtchc 1/1 Terminating 0 12h
12. Create the health check file for the readinessProbe. You can use a for loop again for each action, with updated pod
names. As there are now two containers in the pod, you should include the container name for which one will execute
the command. If no name is given, it will default to the first container. Depending on how you edited the YAML file try1
should be the first pod and goproxy the second. To ensure the correct container is updated, add -c simpleapp to the
kubectl command. Your pod names will be different. Use the names of the newly started containers from the kubectl
get pods command output. Note the >character represents the secondary prompt, you would not type in that character.
student@ckad-1:~$ for name in try1-76cc5ffcc6-4rjvh \
> try1-76cc5ffcc6-bk5f5 try1-76cc5ffcc6-d8n5q \
> try1-76cc5ffcc6-mm6tw try1-76cc5ffcc6-r9q5n \
> try1-76cc5ffcc6-tx4dz
> do
> kubectl exec $name -c simpleapp touch /tmp/healthy
> done
<output_omitted>
13. In the next minute or so the Sidecar container in each pod, which was not running, will change status to Running. Each
should show 2/2 containers running.
try1-76cc5ffcc6-4rjvh 2/2 Running 0 3s
try1-76cc5ffcc6-bk5f5 2/2 Running 0 3s
try1-76cc5ffcc6-d8n5q 2/2 Running 0 3s
try1-76cc5ffcc6-mm6tw 2/2 Running 0 3s
try1-76cc5ffcc6-r9q5n 2/2 Running 0 3s
try1-76cc5ffcc6-tx4dz 2/2 Running 0 3s
14. View the events for a particular pod. Even though both containers are currently running and the pod is in good shape,
note the events section shows the issue.
student@ckad-1:~/app1$ kubectl describe pod try1-76cc5ffcc6-tx4dz | tail
Normal SuccessfulMountVolume 9m kubelet, ckad-1-lab-x6dj
MountVolume.SetUp succeeded for volume "default-token-jf69w"
Normal Pulling 9m kubelet, ckad-1-lab-x6dj
pulling image "10.108.143.90:5000/simpleapp"
28 CHAPTER 3. BUILD
Normal Pulled 9m kubelet, ckad-1-lab-x6dj

Successfully pulled image "10.108.143.90:5000/simpleapp"
Normal Created 9m kubelet, ckad-1-lab-x6dj
Created container
Normal Started 9m kubelet, ckad-1-lab-x6dj
Started container
Normal Pulling 9m kubelet, ckad-1-lab-x6dj
pulling image "k8s.gcr.io/goproxy:0.1"
Normal Pulled 9m kubelet, ckad-1-lab-x6dj
Successfully pulled image "k8s.gcr.io/goproxy:0.1"
Normal Created 9m kubelet, ckad-1-lab-x6dj
Created container
Normal Started 9m kubelet, ckad-1-lab-x6dj
Started container
Warning Unhealthy 4m (x60 over 9m) kubelet, ckad-1-lab-x6dj
Readiness probe failed: cat: /tmp/healthy: No such file or directory
15. If you look for the status of each container in the pod, they should show that both are Running and ready showing True.
student@ckad-1:~/app1$ kubectl describe pod try1-76cc5ffcc6-tx4dz | grep -E 'State|Ready'
State: Running
Ready: True
State: Running
Ready: True
Ready True
Chapter 4
Design
Exercise 4.1: Planning the Deployment
Overview
In this exercise we will investigate common network plugins. Each kubelet agent uses one plugin at a time. Due to
complexity, the entire cluster uses one plugin which is configured prior to application deployment. Some plugins don’t
honor security configurations such as network policies. Should you design a deployment which and use a network
policy there wouldn’t be an error; the policy would have no effect.
While still new, the community is moving towards the Container Network Interface (CNI) specification (https://
github.com/containernetworking/cni). This provides the most flexibility and features in the fast changing space
of container networking.
A common alternative is kubenet, a basic plugin which relies on the cloud provider to handle routing and cross-node
networking. In a previous lab exercise we configured Project Calico. Classic and external modes are also possible.
Several software defined network projects intended for Kubernetes have been created recently, with new features
added regularly.
Evaluate Network Plugins
1. Verify your nodes are using a CNI plugin. Look for options passed to kubelet. You may see other lines including the grep
command itself and a shell script running in a container which configures Calico.
student@ckad-2-nzjr:~$ ps -ef | grep cni
student 13473 13442 0 22:55 pts/1 00:00:00 grep --color=auto cni
root 14118 1 2 Mar30 ? 02:57:27 /usr/bin/kubelet
--bootstrap-kubeconfig=/etc/kubernetes/bootstrap-kubelet.conf
--kubeconfig=/etc/kubernetes/kubelet.conf
--pod-manifest-path=/etc/kubernetes/manifests --allow-privileged=true
--network-plugin=cni --cni-conf-dir=/etc/cni/net.d --cni-bin-dir=/opt/cni/bin
--cluster-dns=10.96.0.10 --cluster-domain=cluster.local
--authorization-mode=Webhook --client-ca-file=/etc/kubernetes/pki/ca.crt
--cadvisor-port=0 --rotate-certificates=true --cert-dir=/var/lib/kubelet/pki
root 30591 30570 0 Mar30 ? 00:00:10 /bin/sh /install-cni.sh
29
30 CHAPTER 4. DESIGN
2. View the details of the install-cni.sh script. The script runs in a container, the path to which will be different than the
example below. Read through the script to see what it does on our behalf.
student@ckad-2-nzjr:~$ sudo find / -name install-cni.sh
/var/lib/docker/aufs/mnt/e95a30499a76e79027502bbb8ee4eeb8464a657e276a493249f573f5d86e19b3/install-cni.sh
/var/lib/docker/aufs/diff/a7cd14de39089493b793f135ec965f0f3f79eeec8f9d78e679d7be1a3bdf3345/install-cni.sh
student@ckad-2-nzjr:~$ sudo less \
/var/lib/docker/aufs/diff/a7cd14de39089493b793f135ec965f0f3f79eeec8f9d78e679d7be1a3bdf3345/install-cni.sh
3. There are many CNI providers possible. The following list represents some of the more common choices, but it is not
exhaustive. With many new plugins being developed there may be another which better serves your needs. Use these
websites to answer questions which follow. While we strive to keep the answers accurate, please be aware that this area
has a lot of attention and development and changes often.
• Project Calico
https://docs.projectcalico.org/v3.0/introduction/
• Calico with Canal
https://docs.projectcalico.org/v3.0/getting-started/kubernetes/installation/hosted/canal
• Weave Works
https://www.weave.works/docs/net/latest/kubernetes/kube-addon
• Flannel
https://github.com/coreos/flannel
• Romana
http://romana.io/how/romana_basics/
• Kube Router
https://www.kube-router.io
• Kopeio
https://github.com/kopeio/networking
4. Which of the plugins allow vxlans?
5. Which are layer 2 plugins?
6. Which are layer 3?
7. Which allow network policies?
8. Which can encrypt all TCP and UDP traffic?
Multi-container Pod Considerations
Using the information learned from this chapter, consider the following questions:
1. Which deployment method would allow the most flexibility, multiple applications per pod or one per pod?
2. Which deployment method allows for the most granular scalability?
3. Which have the best performance?
4. How many IP addresses are assigned per pod?
5. What are some ways containers can communicate within the same pod?
6. What are some reasons you should have multiple containers per pod?
Solution 4.1
31
Plugin Answers
1. Which of the plugins allow vxlans?

Canal, Flannel, Kopeio-networking, Weave Net
2. Which are layer 2 plugins?

Canal, Flannel, Kopeio-networking, Weave Net
3. Which are layer 3?

Project Calico, Romana, Kube Router
4. Which allow network policies?

Project Calico, Canal, Kube Router, Romana Weave Net
5. Which can encrypt all TCP and UDP traffic?

Project Calico, Kopeio, Weave Net
Multi Pod Answers
1. Which deployment method would allow the most flexibility, multiple applications per pod or one per Pod?
One per pod
2. Which deployment method allows for the most granular scalability?

One per pod
3. Which have the best inter-container performance?

Multiple per pod.
4. How many IP addresses are assigned per pod?

One
5. What are some ways containers can communicate within the same pod?
IPC, loopback or shared filesystem access.
6. What are some reasons you should have multiple containers per pod?
Lean containers may not have functionality like logging. Able to maintain lean execution but add functionality
as necessary, like Ambassadors and Sidecar containers.
Exercise 4.2: Designing Applications With Duration: Create a Job
While most applications are deployed such that they continue to be available there are some which we may want to run
a particular number of times called a Job, and others on a regular basis called a CronJob
1. Create a job which will run a container which sleeps for three seconds then stops.
student@ckad-1:~$ vim job.yaml
job.yaml
1 apiVersion: batch/v1
2 kind: Job
3 metadata:
4 name: sleepy
5 spec:
6 completions: 5
7 parallelism: 2
8 activeDeadlineSeconds: 15
9 template:
10 spec:
11 containers:
12 - name: resting
13 image: busybox
14 command: [ "/bin/sleep" ]
15 args: [ "3" ]
16 restartPolicy: Never
2. Create the job, then verify and view the details. The example shows checking the job three seconds in and then again
after it has completed. You may see different output depending on how fast you type.
student@ckad-1:~$ kubectl create -f job.yaml
job.batch/sleepy created
student@ckad-1:~$ kubectl get job
NAME COMPLETIONS DURATION AGE
sleepy 0/1 3s 3s
student@ckad-1:~$ kubectl describe jobs.batch sleepy

Name: sleepy
Namespace: default
Selector: controller-uid=24c91245-d0fb-11e8-947a-42010a800002
Labels: controller-uid=24c91245-d0fb-11e8-947a-42010a800002
job-name=sleepy
Annotations: <none>
Parallelism: 1
Completions: 1
Start Time: Tue, 16 Oct 2018 04:22:50 +0000
Completed At: Tue, 16 Oct 2018 04:22:55 +0000
Duration: 5s
Pods Statuses: 0 Running / 1 Succeeded / 0 Failed

sleepy 1/1 5s 17s
3. View the configuration information of the job. There are three parameters we can use to affect how the job runs. Use
-o yaml to see these parameters. We can see that backoffLimit, completions, and the parallelism. We’ll add
these parameters next.
student@ckad-1:~$ kubectl get jobs.batch sleepy -o yaml
<output_omitted>
uid: c2c3a80d-d0fc-11e8-947a-42010a800002
spec:
backoffLimit: 6
completions: 1
parallelism: 1
selector:
matchLabels:
<output_omitted>
4. As the job continues to AGE in a completion state, delete the job.

student@ckad-1:~$ kubectl delete jobs.batch sleepy
job.batch "sleepy" deleted
33
5. Edit the YAML and add the completions: parameter and set it to 5.
job.yaml
1 student@ckad-1:~$ vim job.yaml
2 <output_omitted>
3 metadata:
4 name: sleepy
5 spec:
6 completions: 5 #<--Add this line
7 template:
8 spec:
9 containers:
10 <output_omitted>
6. Create the job again. As you view the job note that COMPLETIONS begins as zero of 5.
student@ckad-1:~$ kubectl get jobs.batch
sleepy 0/5 5s 5s
7. View the pods that running. Again the output may be different depending on the speed of typing.
nginx-67f8fb575f-g4468 1/1 Running 2 2d
registry-56cffc98d6-xlhhf 1/1 Running 1 2d
sleepy-z5tnh 0/1 Completed 0 8s
sleepy-zd692 1/1 Running 0 3s
<output_omitted>
8. Eventually all the jobs will have completed. Verify then delete the job.
student@ckad-1:~$ kubectl get jobs
sleepy 5/5 26s 10m
9. Edit the YAML again. This time add in the parallelism: parameter. Set it to 2 such that two pods at a time will be
deployed.
student@ckad-1:~$ job job.yaml
job.yaml
1 student@ckad-1:~$ job job.yaml
2 <output_omitted>
3 name: sleepy
4 spec:
5 completions: 5
6 parallelism: 2 #<-- Add this line
7 template:
8 spec:
9 <output_omitted>
10. Create the job again. You should see the pods deployed two at a time until all five have completed.
nginx-67f8fb575f-g4468 1/1 Running 2 2d
registry-56cffc98d6-xlhhf 1/1 Running 1 2d
sleepy-8xwpc 1/1 Running 0 5s
sleepy-xjqnf 1/1 Running 0 5s
try1-c9cb54f5d-b45gl 2/2 Running 0 8h
<output_omitted>
sleepy 3/5 11s 11s
11. Add a parameter which will stop the job after a certain number of seconds. Set the activeDeadlineSeconds: to 15.
The job and all pods will end once it runs for 15 seconds.
<output_omitted>
completions: 5
parallelism: 2
activeDeadlineSeconds: 15 #<-- Add this line
template:
spec:
containers:
- name: resting
image: busybox
command: ["/bin/sleep"]
args: ["3"]
<output_omitted>
12. Delete and recreate the job again. It should run for four times then continue to age without further completions.
sleepy 2/5 6s 6s
sleepy 4/5 16s 16s
13. View the message: entry in the Status section of the object YAML output.
student@ckad-1:~$ kubectl get job sleepy -o yaml
<output_omitted>
status:
conditions:
- lastProbeTime: 2018-10-16T05:45:14Z
lastTransitionTime: 2018-10-16T05:45:14Z
message: Job was active longer than specified deadline
reason: DeadlineExceeded
status: "True"
type: Failed
failed: 1
startTime: 2018-10-16T05:44:59Z
succeeded: 4
14. Delete the job.
35

Exercise 4.3: Designing Applications With Duration: Create a CronJob
A CronJob creates a watch loop which will create a batch job on your behalf when the time becomes true. We Will use
our existing Job file to start.
1. Copy the Job file to a new file.

student@ckad-1:~$ cp job.yaml cronjob.yaml
2. Edit the file to look like the annotated file shown below.
student@ckad-1:~$ vim cronjob.yaml
cronjob.yaml
1 apiVersion: batch/v1beta1 #<-- Add beta1 to be v1beta1

2 kind: CronJob #<-- Change this line
3 metadata:
4 name: sleepy
5 spec:
6 schedule: "*/2 * * * *" #<-- Add Linux style cronjob syntax
7 jobTemplate: #<-- New jobTemplate and spec
8 spec:
9 template: #<-- This and following lines space four to right
10 spec:
11 activeDeadlineSeconds: 10
12 containers:
13 - name: resting
14 image: busybox
15 command: [ "/bin/sleep" ]
16 args: [ "30" ]
17 restartPolicy: Never
3. Create the new CronJob. View the jobs. It will take two minutes for the CronJob to run and generate a new batch Job.
student@ckad-1:~$ kubectl create -f cronjob.yaml
cronjob.batch/sleepy created
student@ckad-1:~$ kubectl get cronjobs.batch
NAME SCHEDULE SUSPEND ACTIVE LAST SCHEDULE AGE
sleepy */2 * * * * False 0 <none> 8s
No resources found.
4. After two minutes you should see jobs start to run.

sleepy */2 * * * * False 0 21s 2m1s
sleepy-1539722040 1/1 5s 18s

sleepy-1539722040 1/1 5s 5m17s
sleepy-1539722160 1/1 6s 3m17s
sleepy-1539722280 1/1 6s 77s
5. Ensure that if the job continues for more than 10 seconds it is terminated. We will first edit the sleep command to run
for 30 seconds then add the activeDeadlineSeconds: entry to the container.
student@ckad-1:~$ vim cronjob.yaml
cronjob.yaml
1 ....
2 jobTemplate:
3 spec:
4 template:
5 spec:
6 activeDeadlineSeconds: 10 #<-- Add this line
7 containers:
8 - name: resting
9 ....
6. Delete and recreate the CronJob. It may take a couple of minutes for the batch Job to be created and terminate due to
the timer.
student@ckad-1:~$ kubectl delete cronjobs.batch sleepy
cronjob.batch "sleepy" deleted
student@ckad-1:~$ kubectl create -f cronjob.yaml
cronjob.batch/sleepy created
sleepy-1539723240 0/1 61s 61s
sleepy */2 * * * * False 1 72s 94s
sleepy-1539723240 0/1 75s 75s
sleepy-1539723240 0/1 2m19s 2m19s
sleepy-1539723360 0/1 19s 19s
sleepy */2 * * * * False 2 31s 2m53s
7. Clean up by deleting the CronJob.

student@ckad-1:~$ kubectl delete cronjobs.batch sleepy
cronjob.batch "sleepy" deleted
Chapter 5
Deployment Configuration
Exercise 5.1: Configure the Deployment: Secrets and ConfigMap
Very Important
Save a copy of your ~/app1/simpleapp.yaml file, in case you would like to repeat portions of the labs, or you find
your file difficult to use due to typos and whitespace issues.
student@ckad-1:~$ cp ~/app1/simpleapp.yaml ~/beforeLab5.yaml
Overview
In this lab we will add resources to our deployment with further configuration you may need for production. We’ll also
work with updating deployed applications and automation of batch jobs and regular tasks.
There are three different ways a ConfigMap can ingest data, from a literal value, from a file, or from a directory of files.
1. Create a ConfigMap containing primary colors. We will create a series of files to ingest into the ConfigMap. First create
a directory primary and populate it with four files. Then we create a file in our home directory with our favorite color.
student@ckad-1:~$ mkdir primary
student@ckad-1:~$ echo c > primary/cyan

student@ckad-1:~$ echo m > primary/magenta
student@ckad-1:~$ echo y > primary/yellow
student@ckad-1:~$ echo k > primary/black
student@ckad-1:~$ echo "known as key" >> primary/black
student@ckad-1:~$ echo blue > favorite
2. Generate a configMap using each of the three methods.

student@ckad-1:~$ kubectl create configmap colors \
--from-literal=text=black \
--from-file=./favorite \
37
38 CHAPTER 5. DEPLOYMENT CONFIGURATION
--from-file=./primary/
configmap/colors created
3. View the newly created configMap. Note the way the ingested data is presented.
student@ckad-1:~$ kubectl get configmap colors
NAME DATA AGE
colors 6 11s
student@ckad-1:~$ kubectl get configmap colors -o yaml
apiVersion: v1
data:
black: |
k
known as key
cyan: |
c
favorite: |
blue
magenta: |
m
text: black
yellow: |
y
kind: ConfigMap
metadata:
creationTimestamp: 2018-04-05T19:49:59Z
name: colors
namespace: default
resourceVersion: "13491"
selfLink: /api/v1/namespaces/default/configmaps/colors
uid: 86457ce3-390a-11e8-ba73-42010a800003
4. Update the YAML file of the application to make use of the configMap as an environmental parameter. Add the six lines
from the env: line to key:favorite.
student@ckad-1:~$ vim app1/simpleapp.yaml
simpleapp.yaml
1 ....
2 spec:
3 containers:
5 env : # Add from here
6 - name: ilike
7 valueFrom:
8 configMapKeyRef:
9 name: colors
10 key: favorite # To here
12 ....
5. Delete and re-create the deployment with the new parameters.

student@ckad-1-lab-7xtx:~$ kubectl delete deployment try1
student@ckad-1-lab-7xtx:~$ kubectl create -f app1/simpleapp.yaml
39
6. Even though the try1 container is not in a ready state, it is running and useful. Use kubectl exec to view a variable’s
value. View the pod state then verify you can see the ilike value within. Note that the use of double dash (- -) tells the
shell to pass the following as standard in.
student@ckad-1:~$ kubectl get po
<output_omitted>
student@ckad-1:~$ kubectl exec -c try1 -it try1-5db9bc6f85-whxbf \
-- /bin/bash -c 'echo $ilike'
blue
7. Edit the YAML file again, this time adding the third method of using a configMap. Edit the file to add three lines.
envFrom should be indented the same amount as env earlier in the file, and configMapRef should be indented the
same as configMapKeyRef.
simpleapp.yaml
1 ....
2 configMapKeyRef:
3 name: colors
4 key: favorite
5 envFrom : #Add this and the following two lines
6 - configMapRef:
7 name: colors
9 ....
8. Again delete and recreate the deployment. Check the pods restart.
student@ckad-1:~$ kubectl create -f app1/simpleapp.yaml
nginx-6b58d9cdfd-9fnl4 1/1 Running 1 23h
registry-795c6c8b8f-hl5w 1/1 Running 2 23h
try1-d4fbf76fd-46pkb 1/2 Running 0 40s
try1-d4fbf76fd-9kw24 1/2 Running 0 39s
try1-d4fbf76fd-bx9j9 1/2 Running 0 39s
try1-d4fbf76fd-jw8g7 1/2 Running 0 40s
try1-d4fbf76fd-lppl5 1/2 Running 0 39s
try1-d4fbf76fd-xtfd4 1/2 Running 0 40s
9. View the settings inside the try1 container of a pod. The following output is truncated in a few places. Omit the container
name to observe the behavior. Also execute a command to see all environmental variables instead of logging into the
container first.
student@ckad-1:~$ kubectl exec -it try1-d4fbf76fd-46pkb -- /bin/bash -c 'env'
Defaulting container name to try1.
Use 'kubectl describe pod/try1-d4fbf76fd-46pkb -n default' to see all of the containers in this pod.
REGISTRY_PORT_5000_TCP_ADDR=10.105.119.236
HOSTNAME=try1-d4fbf76fd-46pkb
TERM=xterm
yellow=y
<output_omitted>
REGISTRY_SERVICE_HOST=10.105.119.236
KUBERNETES_SERVICE_PORT=443
REGISTRY_PORT_5000_TCP=tcp://10.105.119.236:5000
KUBERNETES_SERVICE_HOST=10.96.0.1
text=black
REGISTRY_SERVICE_PORT_5000=5000
<output_omitted>
black=k
known as key
<output_omitted>
ilike=blue
<output_omitted>
magenta=m
cyan=c
<output_omitted>
10. For greater flexibility and scalability ConfigMaps can be created from a YAML file, then deployed and redeployed as
necessary. Once ingested into the cluster the data can be retrieved in the same manner as any other object. Create
another configMap, this time from a YAML file.
student@ckad-1:~$ vim car-map.yaml
car-map.yaml
1 apiVersion: v1
2 kind: ConfigMap
3 metadata:
4 name: fast-car
5 namespace: default
6 data:
7 car.make: Ford
8 car.model: Mustang
9 car.trim: Shelby
student@ckad-1:~$ kubectl create -f car-map.yaml

configmap/fast-car created
11. View the ingested data, note that the output is just as in file created.
student@ckad-1:~$ kubectl get configmap fast-car -o yaml
apiVersion: v1
data:
car.make: Ford
car.model: Mustang
car.trim: Shelby
kind: ConfigMap
metadata:
name: fast-car
namespace: default
selfLink: /api/v1/namespaces/default/configmaps/fast-car
uid: aa19f8f3-39b8-11e8-ba73-42010a800003
12. Add the configMap settings to the simpleapp.yaml file as a volume. Both containers in the try1 deployment can
access to the same volume, using volumeMounts statements. Remember that the volume stanza is of equal depth to
the containers stanza, and should probably come after for readability.
41
simpleapp.yaml
1 ....
2 spec:
3 containers:
5 volumeMounts:
6 - mountPath: /etc/cars
7 name: car-vol
9 name: try1
10 ....
13 volumes : #Add this and following four lines
14 - configMap:
15 defaultMode: 420
16 name: fast-car
17 name: car-vol
18 dnsPolicy: ClusterFirst
19 restartPolicy: Always
20 ....
13. Delete and recreate the deployment.

14. Verify the deployment is running. Note that we still have not automated the creation of the /tmp/healthy file inside the
container, as a result the AVAILABLE count remains zero until we use the for loop to create the file. We will remedy this
in the next step.
student@ckad-1:~$ kubectl get deployment
nginx 1/1 1 1 1d
registry 1/1 1 1 1d
try1 6/6 6 0 39s
15. Our health check was the successful execution of a command. We will edit the command of the existing readinessProbe
to check for the existence of the mounted configMap file and re-create the deployment. After a minute both containers
should become available for each pod in the deployment.
simpleapp.yaml
1 ....
2 readinessProbe:
3 exec:
4 command:
5 - ls #Add/Edit this and following line.
6 - /etc/cars
7 periodSeconds: 5
8 ....

16. Wait about a minute and view the deployment and pods. All six replicas should be running and report that 2/2 containers
are in a ready state within.
student@ckad-1:~$ kubectl get deployment
nginx 1/1 1 1 1d
registry 1/1 1 1 1d
try1 6/6 6 6 1m
nginx-6b58d9cdfd-9fnl4 1/1 Running 1 1d
registry-795c6c8b8f-hl5wf 1/1 Running 2 1d
try1-7865dcb948-2dzc8 2/2 Running 0 1m
try1-7865dcb948-7fkh7 2/2 Running 0 1m
try1-7865dcb948-d85bc 2/2 Running 0 1m
try1-7865dcb948-djrcj 2/2 Running 0 1m
try1-7865dcb948-kwlv8 2/2 Running 0 1m
try1-7865dcb948-stb2n 2/2 Running 0 1m
17. View a file within the new volume mounted in a container. It should match the data we created inside the configMap.
Because the file did not have a carriage-return it will appear prior to the following prompt.
student@ckad-1:~$ kubectl exec -c try1 -it try1-7865dcb948-stb2n \
-- /bin/bash -c 'cat /etc/cars/car.trim'
Shelby student@ckad-1:~$
Exercise 5.2: Configure the Deployment: Attaching Storage

There are several types of storage which can be accessed with Kubernetes, with flexibility of storage being essential to
scalability. In this exercise we will configure an NFS server. With the NFS server we will create a new persistent volume (pv)
and a persistent volume claim (pvc) to use it.
1. Use the CreateNFS.sh script from the tarball to set up NFS on your master node. This script will configure the server,
export /opt/sfw and create a file /opt/sfw/hello.txt.
student@ckad-1:~$ bash ~/lfd259/CreateNFS.sh
Hit:1 http://us-central1.gce.archive.ubuntu.com/ubuntu xenial InRelease
Get:2 http://us-central1.gce.archive.ubuntu.com/ubuntu xenial-updates InRelease [102 kB]
<output_omitted>
Should be ready. Test here and second node
Export list for localhost:

/opt/sfw *
2. Test by mounting the resource from your second node. Begin by installing the client software.
student@ckad-2:~$ sudo apt-get -y install nfs-common nfs-kernel-server
<output_omitted>
3. Test you can see the exported directory using showmount from you second node.
student@ckad-2:~$ showmount -e ckad-1 ## First node’s name or IP
Export list for ckad-1:
/opt/sfw *
4. Mount the directory. Be aware that unless you edit /etc/fstab this is not a persistent mount. Change out the node
name for that of your master node.
43
student@ckad-2:~$ sudo mount ckad-1:/opt/sfw /mnt
5. Verify the hello.txt file created by the script can be viewed.

student@ckad-2:~$ ls -l /mnt
total 4
-rw-r--r-- 1 root root 9 Sep 28 17:55 hello.txt
6. Return to the master node and create a YAML file for an object with kind PersistentVolume. The included example
file needs an edit to the server parameter. Use the hostname of the master server and the directory you created in the
previous step. Only syntax is checked, an incorrect name or directory will not generate an error, but a Pod using the
incorrect resource will not start. Note that the accessModes do not currently affect actual access and are typically used
as labels instead.
student@ckad-1:~$ cd lfd259; vim PVol.yaml
PVol.yaml
1 apiVersion: v1
3 metadata:
4 name: pvvol-1
5 spec:
6 capacity:
7 storage: 1Gi
8 accessModes:
9 - ReadWriteMany
11 nfs:
12 path: /opt/sfw
13 server: ckad-11-1-1-nlsq #<-- Edit to match master node
14 readOnly: false
7. Create and verify you have a new 1Gi volume named pvvol-1. Note the status shows as Available. Remember we
made two persistent volumes for the image registry earlier.
student@ckad-1:~/lfd259$ kubectl create -f PVol.yaml
persistentvolume/pvvol-1 created
student@ckad-1:~/lfd259$ kubectl get pv
NAME CAPACITY ACCESS MODES RECLAIM POLICY STATUS CLAIM STORAGECLASS REASON AGE
pvvol-1 1Gi RWX Retain Available 4s
registryvm 200Mi RWO Retain Bound default/nginx-claim0 4d
task-pv-volume 200Mi RWO Retain Bound default/registry-claim0 4d
8. Now that we have a new volume we will use a persistent volume claim (pvc) to use it in a Pod. We should have two
existing claims from our local registry.
student@ckad-1:~/lfd259$ kubectl get pvc
NAME STATUS VOLUME CAPACITY ACCESS MODES STORAGECLASS AGE
nginx-claim0 Bound registryvm 200Mi RWO 4d
registry-claim0 Bound task-pv-volume 200Mi RWO 4d
9. Create a yaml file with the kind PersistentVolumeClaim.

student@ckad-1:~/lfd259$ vim pvc.yaml
pvc.yaml
1 apiVersion: v1
2 kind: PersistentVolumeClaim
3 metadata:
4 name: pvc-one
5 spec:
6 accessModes:
7 - ReadWriteMany
8 resources:
9 requests:
10 storage: 200Mi
10. Create and verify the new pvc status is bound. Note the size is 1Gi, even though 200Mi was suggested. Only a volume
of at least that size could be used, the first volume with found with at least that much space was chosen.
student@ckad-1:~/lfd259$ kubectl create -f pvc.yaml
persistentvolumeclaim/pvc-one created
student@ckad-1:~/lfd259$ kubectl get pvc
NAME STATUS VOLUME CAPACITY ACCESS MODES STORAGECLASS AGE
nginx-claim0 Bound registryvm 200Mi RWO 4d
pvc-one Bound pvvol-1 1Gi RWX 4s
registry-claim0 Bound task-pv-volume 200Mi RWO 4d
11. Now look at the status of the physical volume. It should also show as bound.
student@ckad-1:~/lfd259$ kubectl get pv ; cd
NAME CAPACITY ACCESS MODES RECLAIM POLICY STATUS
CLAIM STORAGECLASS REASON AGE
pvvol-1 1Gi RWX Retain Bound
default/pvc-one 14m
registryvm 200Mi RWO Retain Bound
default/nginx-claim0 4d
task-pv-volume 200Mi RWO Retain Bound
default/registry-claim0 4d
12. Edit the simpleapp.yaml file to include two new sections. One section for the container while will use the volume mount
point, you should have an existing entry for car-vol. The other section adds a volume to the deployment in general,
which you can put after the configMap volume section.
simpleapp.yaml
1 <output_omitted>
2 volumeMounts:
3 - mountPath: /etc/cars
4 name: car-vol
5 - name: nfs-vol ## Add these two lines
6 mountPath: /opt ##
7
8 <output_omitted>
9 volumes:
10 - configMap:
11 defaultMode: 420
12 name: fast-car
13 name: car-vol
14 - name: nfs-vol ## Add these three lines
15 persistentVolumeClaim: ##
16 claimName: pvc-one ##
17 <output_omitted>
45
13. Delete and re-create the deployment.

student@ckad-1:~/app1$ kubectl delete deployment try1 ; kubectl create -f simpleapp.yaml
14. View the details any of the pods in the deployment, you should see nfs-vol mounted under /opt. The use to command
line completion with the tab key can be helpful for using a pod name.
student@ckad-1:~/app1$ kubectl describe pod try1-594fbb5fc7-5k7sj
<output_omitted>
Mounts:
/etc/cars from car-vol (rw)
/opt from nfs-vol (rw)
<output_omitted>
Exercise 5.3: Using ConfigMaps Configure Ambassador Containers
In an earlier lab we added a second Ambassador container to handle logging. Now that we have learned about using
ConfigMaps and attaching storage we will use configure our basic pod.
1. Review the YAML for our earlier simple pod. Recall that we added an Ambassador style logging container to the pod but
had not fully configured the logging.
student@ckad-1:~$ cat basic.yaml
<output_omitted>
containers:
- name: webcont
image: nginx
ports:
- containerPort: 80
- name: fdlogger
image: k8s.gcr.io/fluentd-gcp:1.30
2. Let us begin by adding shared storage to each container. We will use the hostPath storage class to provide the PV and
PVC. First we create the directory.
student@ckad-1:~$ sudo mkdir /tmp/weblog
3. Now we create a new PV to use that directory for the hostPath storage class. We will use the storageClassName of
manual so that only PVCs which use that name will bind the resource.
student@ckad-1:~$ vim weblog-pv.yaml
weblog-pv.yaml
2 apiVersion: v1
3 metadata:
4 name: weblog-pv-volume
5 labels:
6 type: local
7 spec:
8 storageClassName: manual
9 capacity:
10 storage: 100Mi
11 accessModes:
12 - ReadWriteOnce
13 hostPath:
14 path: "/tmp/weblog"
4. Create and verify the new PV exists.

student@ckad-1:~$ kubectl create -f weblog-pv.yaml
persistentvolume/weblog-pv-volume created
student@ckad-1:~$ kubectl get pv weblog-pv-volume
weblog-pv-volume 100Mi RWO Retain

Available manual 21s
5. Next we will create a PVC to use the PV we just created.

student@ckad-1:~$ vim weblog-pvc.yaml
weblog-pvc.yaml
2 apiVersion: v1
3 metadata:
4 name: weblog-pv-volume
5 labels:
6 type: local
7 spec:
8 storageClassName: manual
9 capacity:
10 storage: 100Mi
11 accessModes:
12 - ReadWriteOnce
13 hostPath:
14 path: "/tmp/weblog"
6. Create the PVC and verify it shows as Bound to the the PV we previously created.
student@ckad-1:~$ kubectl create -f weblog-pvc.yaml
persistentvolumeclaim/weblog-pv-claim created
student@ckad-1:~$ kubectl get pvc weblog-pv-claim
NAME STATUS VOLUME CAPACITY ACCESS MODES
STORAGECLASS AGE
weblog-pv-claim Bound weblog-pv-volume 100Mi RWO
manual 79s
7. We are ready to add the storage to our pod. We will edit three sections. The first will declare the storage to the pod in
general, then two more sections which tell each container where to make the volume available.
student@ckad-1:~$ vim weblog-pvc.yaml
weblog-pvc.yaml
1 apiVersion: v1
2 kind: Pod
3 metadata:
4 name: basicpod
5 labels:
6 type: webserver
7 spec:
8 volumes: #<--Same depth as containers
9 - name: weblog-pv-storage #
10 persistentVolumeClaim: #
47
11 claimName: weblog-pv-claim # name from kubectl get output

12 containers:
13 - name: webcont
14 image: nginx
15 ports:
17 volumeMounts: #<--Same depth as ports
18 - mountPath: "/var/log/nginx/" #
19 name: weblog-pv-storage # Must match volume name above
20 - name: fdlogger
22 volumeMounts: #<--Same depth as image:
23 - mountPath: "/var/log" # We will configure this soon
24 name: weblog-pv-storage # Must match volume name above
8. At this point we can create the pod again. When we create a shell we will find that the access.log for nginx is no
longer a symbolic link pointing to stdout it is a writable, zero length file. Leave a tailf of the log file running. There won’t
be any output until you access the webserver in a following command.
student@ckad-1:~$ kubectl create -f lfd259/basic.yaml
student@ckad-1:~$ kubectl exec -it basicpod -- /bin/bash
Defaulting container name to webcont.
Use 'kubectl describe pod/basicpod -n default' to see all
of the containers in this pod.
root@basicpod:/# ls -l /var/log/nginx/access.log
-rw-r--r-- 1 root root 0 Oct 18 16:12 /var/log/nginx/access.log
root@basicpod:/# tailf /var/log/nginx/access.log
9. Open a second connection to your node. We will use the pod IP as we have not yet configured a service to expose the
pod.
student@ckad-1:~$ kubectl get pods -o wide
NAME READY STATUS RESTARTS AGE IP NODE
NOMINATED NODE
basicpod 2/2 Running 0 3m26s 192.168.213.181 ckad-1
<none>
10. Use curl to view the welcome page of the webserver. When the command completes you should see a new entry added
to the log. Right after the GET we see a 200 response indicating success.
<!DOCTYPE html>
<html>
<head>
<output_omitted>
<New entry in tailf output:>

192.168.32.128 - - [18/Oct/2018:16:16:21 +0000] "GET / HTTP/1.1"
200 612 "-" "curl/7.47.0" "-"
11. Now that we know the webcont container is writing to the PV we will configure the logger to use that directory as a
source. For greater flexibility we will configure fluentd using a configMap. The details of the data settings can be found
in fluentd documentation here: https://docs.fluentd.org/v1.0/categories/config-file
student@ckad-1:~$ vim weblog-configmap.yaml
weblog-pv.yaml
1 apiVersion: v1
2 kind: ConfigMap
3 metadata:
4 name: fluentd-config
5 data:
6 fluentd.conf: |
7 <source>
8 @type tail
9 format none
10 path /var/log/nginx/access.log
11 tag count.format1
12 </source>
13
14 <match *.**>
15 @type forward
16
17 <server>
18 name localhost
19 host 127.0.0.1
20 </server>
21 </match>
12. Create the new configMap.

student@ckad-1:~$ kubectl create -f weblog-configmap.yaml
configmap/fluentd-config created
13. Now we will edit the pod yaml file so that the fluentd container will mount the configmap as a volume and reference the
variables inside the config file. You will add three areas, the volume declaration to the pod, the env parameter and the
mounting of the volume to the fluentd container
basic.yaml
1 ....
2 volumes:
3 - name: weblog-pv-storage
4 persistentVolumeClaim:
5 claimName: weblog-pv-claim
6 - name: log-config #<--Same depth as containers
7 configMap: #
8 name: fluentd-config # Must match existing configMap
9 ....
11 env: #Same depth as image:
12 - name: FLUENTD_ARGS #
13 value: -c /etc/fluentd-config/fluentd.conf #
14 ....
15 volumeMounts:
16 - mountPath: "/var/log"
17 name: weblog-pv-storage
18 - name: log-config #Must match volume name above
19 mountPath: "/etc/fluentd-config" #Directory for env variable
14. At this point we can delete and re-create the pod. If we had a listening agent running on aggregator.example.com we
would see new access message.
49

student@ckad-1:~$ kubectl get pod basicpod
15. Take a log at the logs for both containers. You should see some output for the fdlogger but not for webcont.
Exercise 5.4: Rolling Updates and Rollbacks
When we started working with simpleapp we used a Docker tag called latest. While this is the default tag when
pulling an image, and commonly used, it remains just a string, it may not be the actual latest version of the image.
1. Make a slight change to our source and create a new image. We will use updates and rollbacks with our application.
Adding a comment to the last line should be enough for a new image to be generated.
student@ckad-1:~$ cd ~/app1
student@ckad-1:~/app1$ vim simple.py
<output_omitted>
## Sleep for five seconds then continue the loop
time.sleep(5)
## Adding a new comment so image is different.
2. Build the image again. A new container and image will be created. Verify when successful. There should be a different
image ID and a recent creation time.
student@ckad-1:~/app1$ sudo docker build -t simpleapp .
Sending build context to Docker daemon 7.168 kB
Step 1/3 : FROM python:2
---> 2863c80c418c
Step 2/3 : ADD simple.py /
---> cde8ecf8492b
Removing intermediate container 3e908b76b5b4
Step 3/3 : CMD python ./simple.py
---> Running in 354620c97bf5
---> cc6bba0ea213
Removing intermediate container 354620c97bf5
Successfully built cc6bba0ea213
student@ckad-1:~/app1$ sudo docker images
REPOSITORY TAG
IMAGE ID CREATED SIZE
simpleapp latest
cc6bba0ea213 8 seconds ago 679 MB
10.105.119.236:5000/simpleapp latest
15b5ad19d313 4 days ago 679 MB
<output_omitted>
3. Tag and push the updated image to your locally hosted registry. A reminder your IP address will be different than the
example below. Use the tag v2 this time instead of latest.
student@ckad-1:~/app1$ sudo docker tag simpleapp \
10.105.119.236:5000/simpleapp:v2
student@ckad-1:~/app1$ sudo docker push 10.105.119.236:5000/simpleapp:v2
The push refers to a repository [10.105.119.236:5000/simpleapp]

d6153c8cc7c3: Pushed
ca82a2274c57: Layer already exists
de2fbb43bd2a: Layer already exists
4e32c2de91a6: Layer already exists
6e1b48dc2ccc: Layer already exists
ff57bdb79ac8: Layer already exists
6e5e20cbf4a7: Layer already exists
86985c679800: Layer already exists
8fad67424c4e: Layer already exists
v2: digest: sha256:6cf74051d09463d89f1531fceb9c44cbf99006f8d9b407
dd91d8f07baeee7e9c size: 2218
4. Connect to a terminal running on your second node. Pull the latest image, then pull v2. Note the latest did not pull
the new version of the image. Again, remember to use the IP for your locally hosted registry. You’ll note the digest is
different.
student@ckad-2:~$ sudo docker pull 10.105.119.236:5000/simpleapp
latest: Pulling from simpleapp
Digest: sha256:cefa3305c36101d32399baf0919d3482ae8a53c926688be33
86f9bbc04e490a5
Status: Image is up to date for 10.105.119.236:5000/simpleapp:latest
student@ckad-2:~$ sudo docker pull 10.105.119.236:5000/simpleapp:v2
v2: Pulling from simpleapp
f65523718fc5: Already exists
1d2dd88bf649: Already exists
c09558828658: Already exists
0e1d7c9e6c06: Already exists
c6b6fe164861: Already exists
45097146116f: Already exists
f21f8abae4c4: Already exists
1c39556edcd0: Already exists
fa67749bf47d: Pull complete
Digest: sha256:6cf74051d09463d89f1531fceb9c44cbf99006f8d9b407dd91d8
f07baeee7e9c
Status: Downloaded newer image for 10.105.119.236:5000/simpleapp:v2
5. Use kubectl edit to update the image for the try1 deployment to use v2. As we are only changing one parameter we
could also use the kubectl set command. Note that the configuration file has not been updated, so a delete or a replace
command would not include the new version. It can take the pods up to a minute to delete and to recreate each pod in
sequence.
student@ckad-1:~/app1$ kubectl edit deployment try1
<output_omitted>
containers:
- image: 10.105.119.236:5000/simpleapp:v2
imagePullPolicy: Always
<output_omitted>
6. Verify each of the pods has been recreated and is using the new version of the image. Note some messages will show
the scaling down of the old replicaset, others should show the scaling up using the new image.
student@ckad-1:~/app1$ kubectl get events
LAST SEEN FIRST SEEN COUNT NAME
KIND SUBOBJECT TYPE REASON SOURCE MESSAGE
4s 4s 1 try1-594fbb5fc7-nxhfx.152422073b7084da
Pod spec.containersgoproxy Normal Killing
kubelet, ckad-2-wdrq
Killing container with id docker://goproxy:Need to kill Pod
<output_omitted>
2m 2m 1 try1.1524220c35a0d0fb
Deployment Normal ScalingReplicaSet
51
deployment-controller Scaled up replica set try1-895fccfb to 5

2m 2m 3 try1.1524220e0d69a94a
Deployment
Normal ScalingReplicaSet deployment-controller
(combined from similar events):
Scaled down replica set try1-594fbb5fc7 to 0
7. View the images of a Pod in the deployment. Narrow the output to just view the images. The goproxy remains un-
changed, but the simpleapp should now be v2.
student@ckad-1:~/app1$ kubectl describe pod try1-895fccfb-ttqdn |grep Image
Image: 10.105.119.236:5000/simpleapp:v2
Image ID: docker-pullable://10.105.119.236:5000/simpleapp@sha256:6cf74051d09
463d89f1531fceb9c44cbf99006f8d9b407dd91d8f07baeee7e9c
Image: k8s.gcr.io/goproxy:0.1
Image ID: docker-pullable://k8s.gcr.io/goproxy@sha256:5334c7ad43048e3538775c
b09aaf184f5e8acf4b0ea60e3bc8f1d93c209865a5
8. View the update history of the deployment.

student@ckad-1:~/app1$ kubectl rollout history deployment try1
deployments "try1"
REVISION CHANGE-CAUSE
1 <none>
2 <none>
9. Compare the output of the rollout history for the two revisions. Images and labels should be different, with the image
v2 being the change we made.
student@ckad-1:~/app1$ kubectl rollout history deployment try1 \
--revision=1 > one.out
student@ckad-1:~/app1$ kubectl rollout history deployment try1 \

--revision=2 > two.out
student@ckad-/app11:~$ diff one.out two.out

1c1
< deployments "try1" with revision #1
---
> deployments "try1" with revision #2
3c3
< Labels: pod-template-hash=1509661973
---
> Labels: pod-template-hash=45197796
7c7
< Image: 10.105.119.236:5000/simpleapp:latest
---
> Image: 10.105.119.236:5000/simpleapp:v2
10. View what would be undone using the –dry-run option while undoing the rollout. This allows us to see the new template
prior to using it.
student@ckad-1:~/app1$ kubectl rollout undo --dry-run=true deployment/try1
deployment.extensions/try1
Pod Template:
Labels: pod-template-hash=1509661973
run=try1
Containers:
try1:
Image: 10.105.119.236:5000/simpleapp:latest
Port: <none>
<output_omitted>
11. View the pods. Depending on how fast you type the try1 pods should be about 2 minutes old.

try1-594fbb5fc7-7dl7c 2/2 Running 0 2m
try1-594fbb5fc7-8mxlb 2/2 Running 0 2m
try1-594fbb5fc7-jr7h7 2/2 Running 0 2m
try1-594fbb5fc7-s24wt 2/2 Running 0 2m
try1-594fbb5fc7-xfffg 2/2 Running 0 2m
try1-594fbb5fc7-zfmz8 2/2 Running 0 2m
12. In our case there are only two revisions, which is also the default number kept. Were there more we could choose a
particular version. The following command would have the same effect as the previous, without the –dry-run option.
student@ckad-1:~/app1$ kubectl rollout undo deployment try1 --to-revision=1
deployment.extensions/try1
13. Again, it can take a bit for the pods to be terminated and re-created. Keep checking back until they are all running again.
try1-594fbb5fc7-7dl7c 2/2 Terminating 0 3m
try1-594fbb5fc7-8mxlb 0/2 Terminating 0 2m
try1-594fbb5fc7-jr7h7 2/2 Terminating 0 3m
try1-594fbb5fc7-s24wt 2/2 Terminating 0 2m
try1-594fbb5fc7-xfffg 2/2 Terminating 0 3m
try1-594fbb5fc7-zfmz8 1/2 Terminating 0 2m
try1-895fccfb-8dn4b 2/2 Running 0 22s
try1-895fccfb-kz72j 2/2 Running 0 10s
try1-895fccfb-rxxtw 2/2 Running 0 24s
try1-895fccfb-srwq4 1/2 Running 0 11s
try1-895fccfb-vkvmb 2/2 Running 0 31s
try1-895fccfb-z46qr 2/2 Running 0 31s
Chapter 6
Security
Exercise 6.1: Set SecurityContext for a Pod and Container
Working with Security: Overview

In this lab we will implement security features for new applications, as the simpleapp YAML file is getting long and more
difficult to read. Kubernetes architecture favors smaller, decoupled, and transient applications working together. We’ll
continue to emulate that in our exercises.
In this exercise we will create two new applications. One will be limited in its access to the host node, but have access
to encoded data. The second will use a network security policy to move from the default all-access Kubernetes
policies to a mostly closed network. First we will set security contexts for pods and containers, then create and
consume secrets, then finish with configuring a network security policy.
1. Begin by making a new directory for our second application. Change into that directory.
student@ckad-1:~$ mkdir ~/app2
student@ckad-1:~$ cd ~/app2/
2. Create a YAML file for the second application. In the example below we are using a simple image, busybox, which allows
access to a shell, but not much more. We will add a runAsUser to both the pod as well as the container.
student@ckad-1:~/app2$ vim second.yaml
second.yaml
1 apiVersion: v1
2 kind: Pod
3 metadata:
4 name: secondapp
5 spec:
6 securityContext:
7 runAsUser: 1000
8 containers:
9 - image: busybox
10 name: secondapp
53
54 CHAPTER 6. SECURITY
11 command:
12 - sleep
13 - "3600"
14 securityContext:
15 runAsUser: 2000
16 allowPrivilegeEscalation: false
17 name: busy
3. Create the secondapp pod and verify it’s running. Unlike the previous deployment this application is running as a pod.
Look at the YAML output, to compare and contrast with what a deployment looks like. The status section probably has
the largest contrast.
student@ckad-1:~/app2$ kubectl create -f second.yaml
pod/secondapp created
student@ckad-1:~/app2$ kubectl get pod secondapp
secondapp 1/1 Running 0 21s
student@ckad-1:~/app2$ kubectl get pod secondapp -o yaml
apiVersion: v1
kind: Pod
metadata:
name: secondapp
<output_omitted>
4. Execute a Bourne shell within the Pod. Check the user ID of the shell and other processes. It should show the container
setting, not the pod. This allows for multiple containers within a pod to customize their UID if desired. As there is only
one container in the pod we do not need to use the -c busy option.
student@ckad-1:~/app2$ kubectl exec -it secondapp -- sh
/ $ ps aux
PID USER TIME COMMAND
1 2000 0:00 sleep 3600
8 2000 0:00 sh
12 2000 0:00 ps aux
5. While here check the capabilities of the kernel. In upcoming steps we will modify these values.
/ $ grep Cap /proc/1/status
CapInh: 00000000a80425fb
CapPrm: 0000000000000000
CapEff: 0000000000000000
CapBnd: 00000000a80425fb
CapAmb: 0000000000000000
/ $ exit
6. Use the capability shell wrapper tool, the capsh command, to decode the output. We will view and compare the output
in a few steps. Note that there are 14 comma separated capabilities listed.
student@ckad-1:~/app2$ capsh --decode=00000000a80425fb
0x00000000a80425fb=cap_chown,cap_dac_override,cap_fowner,cap_fsetid,
cap_kill,cap_setgid,cap_setuid,cap_setpcap,cap_net_bind_service,
cap_net_raw,cap_sys_chroot,cap_mknod,cap_audit_write,cap_setfcap
7. Edit the YAML file to include new capabilities for the container. A capability allows granting of specific, elevated priv-
ileges without granting full root access. We will be setting NET ADMIN to allow interface, routing, and other network
configuration. We’ll also set SYS TIME, which allows system clock configuration. More on kernel capabilities can be
read here: https://github.com/torvalds/linux/blob/master/include/uapi/linux/capability.h
It can take up to a minute for the pod to fully terminate, allowing the future pod to be created.
55
student@ckad-1:~/app2$ kubectl delete pod secondapp

pod "secondapp" deleted
second.yaml
1 <output_omitted>
2 - sleep
3 - "3600"
4 securityContext:
5 runAsUser: 2000
7 capabilities: #Add this and following line
8 add: [ "NET_ADMIN" , "SYS_TIME" ]
9 name: busy
8. Create the pod again. Execute a shell within the container and review the Cap settings under /proc/1/status. They
should be different from the previous instance.
student@ckad-1:~/app2$ kubectl exec -it secondapp -- sh
/ $ grep Cap /proc/1/status
CapInh: 00000000aa0435fb
CapPrm: 0000000000000000
CapEff: 0000000000000000
CapBnd: 00000000aa0435fb
CapAmb: 0000000000000000
/ $ exit
9. Decode the output again. Note that the instance now has 16 comma delimited capabilities listed. cap net admin is
listed as well as cap sys time.
student@ckad-1:~/app2$ capsh --decode=00000000aa0435fb
0x00000000aa0435fb=cap_chown,cap_dac_override,cap_fowner,
cap_fsetid,cap_kill,cap_setgid,cap_setuid,cap_setpcap,
cap_net_bind_service,cap_net_admin,cap_net_raw,cap_sys_chroot,
cap_sys_time,cap_mknod,cap_audit_write,cap_setfcap
Exercise 6.2: Create and consume Secrets
Secrets are consumed in a manner similar to ConfigMaps, covered in an earlier lab. While at-rest encryption is just now
enabled, historically a secret was just base64 encoded. There are three types of encryption which can be configured.
1. Begin by generating an encoded password.

student@ckad-1:~/app2$ echo LFTr@1n | base64
TEZUckAxbgo=
2. Create a YAML file for the object with an API object kind set to Secret. Use the encoded key as a password parameter.
student@ckad-1:~/app2$ vim secret.yaml
secret.yaml
1 apiVersion: v1
2 kind: Secret
3 metadata:
4 name: lfsecret
5 data:
6 password: TEZUckAxbgo=
3. Ingest the new object into the cluster.

student@ckad-1:~/app2$ kubectl create -f secret.yaml
secret/lfsecret created
4. Edit secondapp YAML file to use the secret as a volume mounted under /mysqlpassword. Note as there is a command
executed the pod will restart when the command finishes every 3600 seconds, or every hour.
second.yaml
1 <output_omitted>
3 capabilities:
4 add: [ "NET_ADMIN" , "SYS_TIME" ]
5 volumeMounts:
6 - mountPath: /mysqlpassword
7 name: mysql
8 name: busy
9 volumes:
10 - name: mysql
11 secret:
12 secretName: lfsecret

5. Verify the pod is running, then check if the password is mounted where expected. We will find that the password is
available in its clear-text, decoded state.
student@ckad-1:~/app2$ kubectl get pod secondapp
student@ckad-1:~/app2$ kubectl exec -ti secondapp -- /bin/sh
/ $ cat /mysqlpassword/password
LFTr@1n
6. View the location of the directory. Note it is a symbolic link to ../data which is also a symbolic link to another directory.
After taking a look at the filesystem within the container, exit back to the node.
/ $ cd /mysqlpassword/
/mysqlpassword $ ls
password
/mysqlpassword $ ls -al
total 4
drwxrwxrwt 3 root root 100 Apr 11 07:24 .
drwxr-xr-x 21 root root 4096 Apr 11 22:30 ..
57
drwxr-xr-x 2 root root 60 Apr 11 07:24 ..4984_11_04_07_24_47.831222818

lrwxrwxrwx 1 root root 31 Apr 11 07:24 ..data -> ..4984_11_04_07_24_47.831222818
lrwxrwxrwx 1 root root 15 Apr 11 07:24 password -> ..data/password
/mysqlpassword $ exit
Exercise 6.3: Working with ServiceAccounts
We can use ServiceAccounts to assign cluster roles, or the ability to use particular HTTP verbs. In this section we
will create a new ServiceAccount and grant it access to view secrets.
1. Begin by viewing secrets, both in the default namespace as well as all.

student@ckad-1:~$ kubectl get secrets

NAME TYPE DATA AGE
default-token-c4rdg kubernetes.io/service-account-token 3 4d16h
lfsecret Opaque 1 6m5s
student@ckad-1:~$ kubectl get secrets --all-namespaces
NAMESPACE NAME
TYPE DATA AGE
default default-token-c4rdg
kubernetes.io/service-account-token 3 4d16h
kube-public default-token-zqzbg
kube-system attachdetach-controller-token-wxzvc
<output_omitted>
2. We can see that each agent uses a secret in order to interact with the API server. We will create a new ServiceAccount
which will have access.
student@ckad-1:~$ vim serviceaccount.yaml
serviceaccount.yaml
1 apiVersion: v1
2 kind: ServiceAccount
3 metadata:
4 name: secret-access-sa
student@ckad-1:~$ kubectl create -f serviceaccount.yaml

serviceaccount/secret-access-sa created
student@ckad-1:~$ kubectl get serviceaccounts
NAME SECRETS AGE
default 1 4d17h
secret-access-sa 1 34s
3. Now we will create a ClusterRole which will list the actual actions allowed cluster-wide. We will look at an existing role
to see the syntax.
student@ckad-1:~$ kubectl get clusterroles
NAME AGE
admin 4d17h
calico-cni-plugin 4d17h
calico-kube-controllers 4d17h
cluster-admin 4d17h
<output_omitted>
4. View the details for the admin and compare it to the cluster-admin. The admin has particular actions allowed, but
cluster-admin has the meta-character ’*’ allowing all actions.
student@ckad-1:~$ kubectl get clusterroles admin -o yaml
<output_omitted>
student@ckad-1:~$ kubectl get clusterroles cluster-admin -o yaml
<output_omitted>
5. Using some of the output above, we will create our own file.
student@ckad-1:~$ vim clusterrole.yaml
clusterrole.yaml
1 apiVersion: rbac.authorization.k8s.io/v1beta1
2 kind: ClusterRole
3 metadata:
4 name: secret-access-cr
5 rules:
6 - apiGroups:
7 - ""
8 resources:
9 - secrets
10 verbs:
11 - get
12 - list
6. Create and verify the new ClusterRole.

student@ckad-1:~$ kubectl create -f clusterrole.yaml
clusterrole.rbac.authorization.k8s.io/secret-access-cr created
student@ckad-1:~$ kubectl get clusterrole secret-access-cr -o yaml
apiVersion: rbac.authorization.k8s.io/v1
kind: ClusterRole
metadata:
name: secret-access-cr
<output_omitted>
7. Now we bind the role to the account. Create another YAML file which uses roleRef::
student@ckad-1:~$ vim rolebinding.yaml
rolebinding.yaml
2 kind: RoleBinding
3 metadata:
4 name: secret-rb
5 subjects:
6 - kind: ServiceAccount
7 name: secret-access-sa
8 roleRef:
9 kind: ClusterRole
10 name: secret-access-cr
11 apiGroup: rbac.authorization.k8s.io
59
8. Create the new RoleBinding and verify.

student@ckad-1:~$ kubectl create -f rolebinding.yaml
rolebinding.rbac.authorization.k8s.io/secret-rb created
student@ckad-1:~$ kubectl get rolebindings
NAME AGE
secret-rb 17s
9. View the secondapp pod and grep for secret settings. Note that it uses the default settings.
student@ckad-1:~$ kubectl describe pod secondapp |grep -i secret
/var/run/secrets/kubernetes.io/serviceaccount from
default-token-c4rdg (ro)
Type: Secret (a volume populated by a Secret)
SecretName: default-token-c4rdg
10. Edit the second.yaml file and add the use of the serviceAccount.
student@ckad-1:~$ vim second.yaml
second.yaml
1 ....
2 name: secondapp
3 spec:
4 serviceAccountName: secret-access-sa #<-- Add this line
5 securityContext:
6 runAsUser: 1000
7 ....
11. We will delete the secondapp pod if still running, then create it again. View what the secret is by default.
student@ckad-1:~$ kubectl delete pod secondapp ; \
kubectl create -f second.yaml
student@ckad-1:~$ kubectl describe pod secondapp |grep -i secret
/var/run/secrets/kubernetes.io/serviceaccount from
secret-access-sa-token-wd7vm (ro)
secret-access-sa-token-wd7vm:
Type: Secret (a volume populated by a Secret)
SecretName: secret-access-sa-token-wd7vm
Exercise 6.4: Implement a NetworkPolicy
An early architecture decision with Kubernetes was non-isolation, that all pods were able to connect to all other pods
and nodes by design. In more recent releases the use of a NetworkPolicy allows for pod isolation. The policy only has
effect when the network plugin, like Project Calico, are capable of honoring them. If used with a plugin like flannel they
will have no effect. The use of matchLabels allows for more granular selection within the namespace which can be se-
lected using a namespaceSelector. Using multiple labels can allow for complex application of rules. More information
can be found here: https://kubernetes.io/docs/concepts/services-networking/network-policies
1. Begin by creating a default policy which denies all traffic. Once ingested into the cluster this will affect every pod not
selected by another policy, creating a mostly-closed environment. If you want to only deny ingress or egress traffic you
can remove the other policyType.
student@ckad-1:~/app2$ vim allclosed.yaml
allclosed.yaml
1 apiVersion: networking.k8s.io/v1
2 kind: NetworkPolicy
3 metadata:
4 name: deny-default
5 spec:
6 podSelector: {}
7 policyTypes:
8 - Ingress
9 - Egress
2. Before we can test the new network policy we need to make sure network access works without it applied. Update
secondapp to include a new container running nginx, then test access. Begin by adding two lines for the nginx image
and name webserver, as found below. It takes a bit for the pod to terminate, so we’ll delete then edit the file.
second.yaml
1 apiVersion: v1
2 kind: Pod
3 metadata:
4 name: secondapp
5 spec:
6 securityContext:
7 runAsUser: 1000
8 containers:
9 - image: busybox
10 name: secondapp
11 command:
12 - sleep
13 - "3600"
14 securityContext:
15 runAsUser: 2000
17 name: busy
3. Create the new pod. Be aware the pod will move from ContainerCreating to Error to CrashLoopBackOff, as only one
of the containers will start. We will troubleshoot the error in following steps.
date-1523648520-z282m 0/1 Completed 0 3m
date-1523648580-zznjs 0/1 Completed 0 2m
date-1523648640-2h6qt 0/1 Completed 0 1m
date-1523648700-drfp5 1/1 Running 0 18s
Registry-795c6c8b8f-hl5wf 1/1 Running 2 8d
secondapp 1/2 CrashLoopBackOff 1 13s
4. Take a closer look at the events leading up to the failure. The images were pulled and the container was started. It was
the full execution of the container which failed.
61
student@ckad-1:~/app2$ kubectl get event

<output_omitted>
Normal Created kubelet, ckad-2-wdrq Created container
5m 5m secondapp.1525166daeeb0e43
Pod spec.containersbusy Normal Started
kubelet, ckad-2-wdrq Started container
20s 5m 25 secondapp.1525166e5791a7fd
Pod spec.containerswebserver Warning BackOff
kubelet, ckad-2-wdrq Back-off restarting failed container
5. View the logs of the webserver container mentioned in the previous output. Note there are errors about the user
directive and not having permission to make directories.
student@ckad-1:~/app2$ kubectl logs secondapp webserver
2018/04/13 19:51:13 [warn] 1#1: the "user" directive makes sense
only if the master process runs with super-user privileges,
ignored in /etc/nginx/nginx.conf:2
nginx: [warn] the "user" directive makes sense only if the master
process runs with super-user privileges,
ignored in /etc/nginx/nginx.conf:2
2018/04/13 19:51:13 [emerg] 1#1: mkdir() "/var/cache/nginx/client_temp"
failed (13: Permission denied)
nginx: [emerg] mkdir() "/var/cache/nginx/client_temp" failed
(13: Permission denied)
6. Delete the pods. Edit the YAML file to comment out the setting of a UID for the entire pod.
student@ckad-1:~/app2$ kubectl delete -f second.yaml
second.yaml
1 apiVersion: v1
2 kind: Pod
3 metadata:
4 name: secondapp
5 spec:
6 securityContext:
7 runAsUser: 1000
8 containers:
9 - image: busybox
10 name: secondapp
11 command:
12 - sleep
13 - "3600"
14 securityContext:
15 runAsUser: 2000
17 name: busy
7. Create the pod again. This time both containers should run. You may have to wait for the previous pod to fully terminate,
depending on how fast you type.
<output_omitted>
8. Expose the webserver using a NodePort service. Expect an error due to lack of labels.
student@ckad-1:~/app2$ kubectl expose pod secondapp --type=NodePort --port=80
error: couldn't retrieve selectors via --selector flag or
introspection: the pod has no labels and cannot be exposed
See 'kubectl expose -h' for help and examples.
9. Edit the YAML file to add a label in the metadata, adding the example: second label right after the pod name. Note you
can delete several resources at once by passing the YAML file to the delete command. Delete and recreate the pod. It
may take up to a minute for the pod to shut down.
student@ckad-1:~/app2$ kubectl delete -f second.yaml
apiVersion: v1
kind: Pod
metadata:
name: secondapp
labels:
example: second
spec:
# securityContext:
# runAsUser: 1000
<output_omitted>
<output_omitted>
10. This time we will expose a NodePort again, and create the service separately, then add a label to illustrate how labels
are essential for tying resources together inside of kubernetes.
student@ckad-1:~/app2$ kubectl create service nodeport secondapp --tcp=80
service/secondapp created
11. Look at the details of the service. Note the selector is set to app: secondapp. Also take note of the nodePort, which is
31655 in the example below, yours may be different.
student@ckad-1:~/app2$ kubectl get svc secondapp -o yaml
apiVersion: v1
kind: Service
metadata:
labels:
app: secondapp
name: secondapp
namespace: default
selfLink: /api/v1/namespaces/default/services/secondapp
uid: 0aeaea82-441e-11e8-ac6e-42010a800007
spec:
clusterIP: 10.97.96.75
externalTrafficPolicy: Cluster
ports:
- name: "80"
nodePort: 31655
port: 80
protocol: TCP
targetPort: 80
63
selector:
app: secondapp
sessionAffinity: None
type: NodePort
status:
loadBalancer:
12. Test access to the service using curl and the ClusterIP shown in the previous output. As the label does not match any
other resources, the curl command should hang and eventually timeout. Use control-c to exit back to the shell.
student@ckad-1:~/app2$ curl http://10.97.96.75
13. Edit the service. We will change the label to match secondapp, and set the nodePort to a new port, one that may have
been specifically opened by our firewall team, port 32000.
student@ckad-1:~/app2$ kubectl edit svc secondapp
<output_omitted>
ports:
- name: "80"
nodePort: 32000 ## Edit this line
port: 80
protocol: TCP
targetPort: 80
selector:
example: second ## Edit this line, too
sessionAffinity: None
<output_omitted>
14. Verify the updated port number is showing properly, and take note of the ClusterIP. The example below shows a ClusterIP
of 10.97.96.75 and a port of 32000 as expected.
student@ckad-1:~/app2$ kubectl get svc
<output_omitted>
secondapp NodePort 10.97.96.75 <none> 80:32000/TCP 5m
15. Test access to the high port. You should get the default nginx welcome page both if you test from the node to the
ClusterIP:<low-port-number> and from the exterior hostIP:high-port-number>. As the high port is randomly
generated make sure it’s available. Both of your nodes should be exposing the web server on port 32000.
<!DOCTYPE html>
<html>
<head>
<output_omitted>
[user@laptop ~]$ curl http://35.184.219.5:32000
<!DOCTYPE html>
<html>
<head>
<output_omitted>
16. Now test egress from a container to the outside world. We’ll use the netcat command to verify access to a running web
server on port 80. First test local access to nginx, then a remote server.
student@ckad-1:~/app2$ kubectl exec -it -c busy secondapp sh
/ $ nc -vz 127.0.0.1 80
127.0.0.1 (127.0.0.1:80) open
/ $ nc -vz www.linux.com 80
www.linux.com (151.101.185.5:80) open
/ $ exit
Exercise 6.5: Testing the Policy
1. Now that we have tested both ingress and egress we can implement the network policy.
student@ckad-1:~/app2$ kubectl create -f allclosed.yaml
networkpolicy.networking.k8s.io/deny-default created
2. Use the ingress and egress tests again. Three of the four should eventually timeout. Start by testing from outside the
cluster.
[user@laptop ~]$ curl http://35.184.219.5:32215
curl: (7) Failed to connect to 35.184.219.5 port
32000: Connection timed out
3. Then test from the host to the container.

student@ckad-1:~/app2$ curl http://10.97.96.75:80
curl: (7) Failed to connect to 10.97.96.75 port 80: Connection timed out
4. Now test egress. From container to container should work, as the filter is outside of the pod. Then test egress to an
external web page. It should eventually timeout.
/ $ nc -vz 127.0.0.1 80
127.0.0.1 (127.0.0.1:80) open
nc: bad address 'www.linux.com'
/ $ exit
5. Update the NetworkPolicy and comment out the Egress line. Then replace the policy.
allclosed.yaml
1 ....
2 # - Egress
student@ckad-1:~/app2$ kubectl replace -f allclosed.yaml

networkpolicy.networking.k8s.io/deny-default replaced
6. Test egress access to an outside site. Get the IP address of the eth0 inside the container while logged in. The IP is
192.168.55.91 in the example below, yours may be different.
www.linux.com (151.101.185.5:80) open
/ $ ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
2: tunl0@NONE: <NOARP> mtu 1480 qdisc noop qlen 1000
link/ipip 0.0.0.0 brd 0.0.0.0
4: eth0@if59: <BROADCAST,MULTICAST,UP,LOWER_UP,M-DOWN> mtu 1500 qdisc noqueue
link/ether 1e:c8:7d:6a:96:c3 brd ff:ff:ff:ff:ff:ff
65
inet 192.168.55.91/32 scope global eth0

inet6 fe80::1cc8:7dff:fe6a:96c3/64 scope link
/ $ exit
7. Now add a selector to allow ingress to only the nginx container. Use the IP from the eth0 range.
allclosed.yaml
1 <output_omitted>
2 policyTypes:
3 - Ingress
4 ingress:
5 - from:
6 - ipBlock:
7 cidr: 192.168.0.0/16
8. Recreate the policy, and verify its configuration.

student@ckad-1:~/app2$ kubectl get networkpolicy
NAME POD-SELECTOR AGE
deny-default <none> 15s
student@ckad-1:~/app2$ kubectl get networkpolicy -o yaml
apiVersion: v1
items:
- apiVersion: extensions/v1beta1
kind: NetworkPolicy
metadata:
<output_omitted>
9. Test access to the container both using curl as well as ping, the IP address to use was found from the IP inside the
container.
<!DOCTYPE html>
<html>
<head>
<output_omitted>
student@ckad-1:~/app2$ ping -c5 192.168.55.91
PING 192.168.55.91 (192.168.55.91) 56(84) bytes of data.
64 bytes from 192.168.55.91: icmp_seq=1 ttl=63 time=1.11 ms
--- 192.168.55.91 ping statistics ---

5 packets transmitted, 5 received, 0% packet loss, time 4054ms
rtt min/avg/max/mdev = 0.295/0.495/1.119/0.312 ms
10. Update the policy to only allow ingress for TCP traffic on port 80, then test with curl, which should work. The ports entry
should line up with the from entry a few lines above.
allclosed.yaml
1 <output_omitted>
2 - Ingress
3 ingress:
4 - from:
5 - ipBlock:
6 cidr: 192.168.0.0/16
7 ports:
8 - port: 80
9 protocol: TCP

<!DOCTYPE html>
<html>
<head>
<output_omitted>
11. All five pings should fail, with zero received.

student@ckad-1:~/app2$ ping -c5 192.168.55.91
PING 192.168.55.91 (192.168.55.91) 56(84) bytes of data.
--- 192.168.55.91 ping statistics ---

5 packets transmitted, 0 received, 100% packet loss, time 4098ms
Chapter 7
Exposing Applications
Exercise 7.1: Exposing Applications: Expose a Service
Overview
In this lab we will explore various ways to expose an application to other pods and outside the cluster. We will add to
the NodePort used in previous labs other service options.
1. We will begin by using the default service type ClusterIP. This is a cluster internal IP, only reachable from within the
cluster. Begin by viewing the existing services.
kubernetes ClusterIP 10.96.0.1 <none> 443/TCP 8d
nginx ClusterIP 10.108.95.67 <none> 443/TCP 8d
registry ClusterIP 10.105.119.236 <none> 5000/TCP 8d
secondapp NodePort 10.111.26.8 <none> 80:32000/TCP 7h
2. Delete the existing service for secondapp.

student@ckad-1:~/app2$ kubectl delete svc secondapp
service "secondapp" deleted
3. Create a YAML file for a replacement service, which would be persistent. Use the label to select the secondapp. Expose
the same port and protocol of the previous service.
student@ckad-1:~/app2$ vim service.yaml
service.yaml (Version 1)
1 apiVersion: v1
2 kind: Service
3 metadata:
4 name: secondapp
5 labels:
6 run: my-nginx
7 spec:
67
68 CHAPTER 7. EXPOSING APPLICATIONS
8 ports:
9 - port: 80
10 type: NodePort
11 selector:
12 example: second
4. Create the service, find the new IP and port. Note there is no high number port as this is internal access only.
student@ckad-1:~/app2$ kubectl create -f service.yaml
secondapp ClusterIP 10.98.148.52 <none> 80/TCP 14s
5. Test access. You should see the default welcome page again.
<!DOCTYPE html>
<html>
<head>
<output_omitted>
6. To expose a port to outside the cluster we will create a NodePort. We had done this in a previous step from the
command line. When we create a NodePort it will create a new ClusterIP automatically. Edit the YAML file again. Add
type: NodePort. Also add the high-port to match an open port in the firewall as mentioned in the previous chapter. You’ll
have to delete and re-create as the existing IP is immutable, but not able to be reused. The NodePort will try to create a
new ClusterIP instead.
service.yaml (Version 1)
1 apiVersion: v1
2 kind: Service
3 metadata:
4 name: secondapp
5 labels:
6 run: my-nginx
7 spec:
8 ports:
9 - port: 80
10 protocol: TCP
11 nodePort: 32000
12 type: NodePort
13 selector:
14 example: second
student@ckad-1:~/app2$ kubectl delete svc secondapp ; kubectl create -f service.yaml

7. Find the new ClusterIP and ports for the service.

69

secondapp NodePort 10.109.134.221 <none> 80:32000/TCP 4s
8. Test the low port number using the new ClusterIP for the secondapp service.
student@ckad-1:~/app2$ curl 10.109.134.221
<!DOCTYPE html>
<html>
<head>
<output_omitted>
9. Test access from an external node to the host IP and the high container port. Your IP and port will be different. It should
work, even with the network policy in place, as the traffic is arriving via a 192.168.0.0 port.
user@laptop:~/Desktop$ curl http://35.184.219.5:32000
<!DOCTYPE html>
<html>
<head>
<output_omitted>
10. The use of a LoadBalancer makes an asynchronous request to an external provider for a load balancer if one is available.
It then creates a NodePort and waits for a response including the external IP. The local NodePort will work even before
the load balancer replies. Edit the YAML file and change the type to be LoadBalancer.
service.yaml
1 <output_omitted>
2 - port: 80
3 protocol: TCP
4 type: LoadBalancer
5 selector:
6 example: second
student@ckad-1:~/app2$ kubectl delete svc secondapp

student@ckad-1:~/app2$ kubectl create -f service.yaml
11. As mentioned the cloud provider is not configured to provide a load balancer; the External-IP will remain in pending
state. Some issues have been found using this with VirtualBox.
secondapp LoadBalancer 10.109.26.21 <pending> 80:32000/TCP 4s
12. Test again local and from a remote node. The IP addresses and ports will be different on your node.
serewic@laptop:~/Desktop$ curl http://35.184.219.5:32000
<!DOCTYPE html>
<html>
<head>
<output_omitted>
Exercise 7.2: Ingress Controller
If you have a large number of services to expose outside of the cluster, or to expose a low-number port on the host
node you can deploy an ingress controller. While nginx and GCE have controllers officially supported by Kubernetes.io,
the Traefik Ingress Controller is easier to install. At the moment.
1. As we have RBAC configured we need to make sure the controller will run and be able to work with all necessary ports,
endpoints and resources. Create a YAML file to declare a clusterrole and a clusterrolebinding
student@ckad-1:~/app2$ vim ingress.rbac.yaml
ingress.rbac.yaml
1 kind: ClusterRole
3 metadata:
4 name: traefik-ingress-controller
5 rules:
6 - apiGroups:
7 - ""
8 resources:
9 - services
10 - endpoints
11 - secrets
12 verbs:
13 - get
14 - list
15 - watch
16 - apiGroups:
17 - extensions
18 resources:
19 - ingresses
20 verbs:
21 - get
22 - list
23 - watch
24 ---
25 kind: ClusterRoleBinding
27 metadata:
29 roleRef:
30 apiGroup: rbac.authorization.k8s.io
31 kind: ClusterRole
33 subjects:
34 - kind: ServiceAccount
36 namespace: kube-system
2. Create the new role and binding.

student@ckad-1:~/app2$ kubectl create -f ingress.rbac.yaml
clusterrole.rbac.authorization.k8s.io/traefik-ingress-controller created
clusterrolebinding.rbac.authorization.k8s.io/traefik-ingress-controller created
71
3. Create the Traefik controller. We will use a script directly from their website. The shorter, easier URL for the following is:
https://goo.gl/D2uEEF. We will need to download the script and make some edits before creating the objects.
student@ckad-1:~/app2$ wget \
https://raw.githubusercontent.com/containous/traefik/master/examples/k8s/traefik-ds.yaml
4. Edit the downloaded file. The output below represents the changes in a diff type output, from the downloaded to the
edited file. One line should be added, six lines should be removed.
student@ckad-1:~/app2$ vim traefik-ds.yaml
traefik-ds.rule.yaml
1 23a24 ## Add the following line 24
2 > hostNetwork: true
3 34,39d34 ## Remove these lines around line 34
4 < securityContext:
5 < capabilities:
6 < drop:
7 < - ALL
8 < add:
9 < - NET_BIND_SERVICE
The file should look like this:
traefik-ds.rule.yaml
1 ....
2 terminationGracePeriodSeconds: 60
3 hostNetwork: True
4 containers:
5 - image: traefik
6 name: traefik-ingress-lb
7 ports:
8 - name: http
9 containerPort: 80
10 hostPort: 80
11 - name: admin
12 containerPort: 8080
13 hostPort: 8080
14 args:
15 - --api
16 ....
5. Create the objects using the edited file.

student@ckad-1:~/app2$ kubectl apply -f traefik-ds.yaml
serviceaccount/traefik-ingress-controller created
daemonset.extensions/traefik-ingress-controller created
service/traefik-ingress-service created
6. Now that there is a new controller we need to pass some rules, so it knows how to handle requests. Note that the host
mentioned is www.example.com, which is probably not your node name. We will pass a false header when testing. Also
the service name needs to match the secondapp we’ve been working with.
student@ckad-1:~/app2$ vim ingress.rule.yaml
ingress.rule.yaml
1 apiVersion: extensions/v1beta1
2 kind: Ingress
3 metadata:
4 name: ingress-test
5 annotations:
6 kubernetes.io/ingress.class: traefik
7 spec:
8 rules:
9 - host: www.example.com
10 http:
11 paths:
12 - backend:
13 serviceName: secondapp
14 servicePort: 80
15 path: /
7. Now ingest the rule into the cluster.

student@ckad-1:~/app2$ kubectl create -f ingress.rule.yaml
ingress.extensions/ingress-test created
8. We should be able to test the internal and external IP addresses, and see the nginx welcome page. The loadbalancer
would present the traffic, a curl request in this case, to the externally facing interface. Use ip a to find the IP address
of the interface which would face the load balancer. In this example the interface would be ens4, and the IP would be
10.128.0.7.
student@ckad-1:~$ ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
inet6 ::1/128 scope host
2: ens4: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1460 qdisc mq state UP group default qlen 1000
link/ether 42:01:0a:80:00:03 brd ff:ff:ff:ff:ff:ff
inet 10.128.0.7/32 brd 10.128.0.3 scope global ens4
<output_omitted>
student@ckad-1:~/app2$ curl -H "Host: www.example.com" http://10.128.0.7/
<!DOCTYPE html>
<html>
<head>
<style>
user@laptop:~$ curl -H "Host: www.example.com" http://35.193.3.179
<!DOCTYPE html>
<html>
<head>
<style>
<output_omitted>
9. At this point we would keep adding more and more web servers. We’ll configure one more, which would then be a
process continued as many times as desired. Begin by deploying another nginx server. Give it a label and expose port
80.
student@ckad-1:~/app2$ kubectl run thirdpage --image=nginx --port=80 -l example=third
deployment.apps "thirdpage" created
73
10. Expose the new server as a NodePort.

student@ckad-1:~/app2$ kubectl expose deployment thirdpage --type=NodePort
service "thirdpage" exposed
11. Now we will customize the installation. Run a bash shell inside the new pod. Your pod name will end differently. Install
vim inside the container then edit the index.html file of nginx so that the title of the web page will be Third Page.
student@ckad-1:~/app2$ kubectl exec -it thirdpage-5cf8d67664-zcmfh -- /bin/bash
root@thirdpage-5cf8d67664-zcmfh:/# apt-get update
root@thirdpage-5cf8d67664-zcmfh:/# apt-get install vim -y
root@thirdpage-5cf8d67664-zcmfh:/# vim /usr/share/nginx/html/index.html

<!DOCTYPE html>
<html>
<head>
<title>Third Page</title>
<style>
<output_omitted>
12. Edit the ingress rules to point the thirdpage service.

student@ckad-1:~/app2$ kubectl edit ingress ingress-test
<output_omitted>
- host: www.example.com
http:
paths:
- backend:
serviceName: secondapp
servicePort: 80
path: /
- host: thirdpage.org
http:
paths:
- backend:
serviceName: thirdpage
servicePort: 80
path: /
status:
<output_omitted>
13. Test the second hostname using curl locally as well as from a remote system.
student@ckad-1:~/app2$ curl -H "Host: thirdpage.org" http://10.128.0.7/
<!DOCTYPE html>
<html>
<head>
<title>Third Page</title>
<style>
<output_omitted>
Chapter 8
Troubleshooting
Exercise 8.1: Troubleshooting: Monitor Applications
Overview
Troubleshooting can be difficult in a multi-node, decoupled and transient environment. Add in the rapid pace of change
and it becomes more difficult. Instead of focusing and remembering a particular error and the fix it may be more useful
to learn a flow of troubleshooting and revisit assumptions until the pace of change slows and various areas further
mature.
1. View the secondapp pod, it should show as Running. This may not mean the application within is working properly, but
that the pod is running. The restarts are due to the command we have written to run. The pod exists when done, and
the controller restarts another container inside. The count depends on how long the labs have been running.
student@ckad-1/app1:~$ cd
student@ckad-1:~$ kubectl get pods secondapp
secondapp 2/2 Running 49 2d
2. Look closer at the pod. Working slowly through the output check each line. If you have issues, are other pods having
issues on the same node or volume? Check the state of each container. Both busy and webserver should report as
Running. Note webserver has a restart count of zero while busy has a restart count of 49. We expect this as, in our
case, the pod has been running for 49 hours.
student@ckad-1:~$ kubectl describe pod secondapp
Name: secondapp
Namespace: default
Node: ckad-2-wdrq/10.128.0.2
Start Time: Fri, 13 Apr 2018 20:34:56 +0000
Labels: example=second
Annotations: <none>
Status: Running
IP: 192.168.55.91
Containers:
webserver:
<output_omitted>
State: Running
Started: Fri, 13 Apr 2018 20:34:58 +0000
75
76 CHAPTER 8. TROUBLESHOOTING
Ready: True
Restart Count: 0
<output_omitted>
busy:
<output_omitted>
State: Running
Started: Sun, 15 Apr 2018 21:36:20 +0000
Last State: Terminated
Reason: Completed
Exit Code: 0
Started: Sun, 15 Apr 2018 20:36:18 +0000
Finished: Sun, 15 Apr 2018 21:36:18 +0000
Ready: True
Restart Count: 49
Environment: <none>
3. There are three values for conditions. Check that the pod reports Initialized, Ready and scheduled.
<output_omitted>
Conditions:
Type Status
Initialized True
Ready True
PodScheduled True
<output_omitted>
4. Check if there are any events with errors or warnings which may indicate what is causing any problems.
Events:
Type Reason Age From Message
---- ------ ---- ---- -------
Normal Pulling 34m (x50 over 2d) kubelet, ckad-2-wdrq pulling
image "busybox"
Normal Pulled 34m (x50 over 2d) kubelet, ckad-2-wdrq Successfully
pulled image "busybox"
Normal Created 34m (x50 over 2d) kubelet, ckad-2-wdrq Created
container
Normal Started 34m (x50 over 2d) kubelet, ckad-2-wdrq Started
container
5. View each container log. You may have to sift errors from expected output. Some containers may have no output at all,
as is found with busy.
student@ckad-1:~$ kubectl logs secondapp webserver
192.168.55.0 - - [13/Apr/2018:21:18:13 +0000] "GET / HTTP/1.1" 200
612 "-" "curl/7.47.0" "-"
192.168.55.0 - - [13/Apr/2018:21:20:35 +0000] "GET / HTTP/1.1" 200
612 "-" "curl/7.53.1" "-"
127.0.0.1 - - [13/Apr/2018:21:25:29 +0000] "GET" 400 174 "-" "-" "-"
127.0.0.1 - - [13/Apr/2018:21:26:19 +0000] "GET index.html" 400 174
"-" "-" "-"
<output_omitted>
student@ckad-1:~$ kubectl logs secondapp busy
student@ckad-1:~$
6. Check to make sure the container is able to use DNS and communicate with the outside world. Remember we still have
limited the UID for secondapp to be UID 2000, which may prevent some commands from running. It can also prevent
an application from completing expected tasks.
student@ckad-1:~$ kubectl exec -it secondapp -c busy -- sh
/ $ nslookup www.linux.com
77
Server: 10.96.0.10
Address 1: 10.96.0.10 kube-dns.kube-system.svc.cluster.local
Name: www.linux.com
Address 1: 151.101.45.5
/ $ cat /etc/resolv.conf
nameserver 10.96.0.10
search default.svc.cluster.local svc.cluster.local
cluster.local c.endless-station-188822.internal
google.internal
options ndots:5
7. Test access to a remote node using nc (NetCat). There are several options to nc which can help troubleshoot if the
problem is the local node, something between nodes or in the target. In the example below the connect never completes
and a control-c was used to interrupt.
/ $ nc www.linux.com 25
^Cpunt!
8. Test using an IP address in order to narrow the issue to name resolution. In this case the IP in use is a well known
IP for Google’s DNS servers. The following example shows that Internet name resolution is working, but our UID issue
prevents access to the index.html file.
/ $ wget http://www.linux.com/
Connecting to www.linux.com (151.101.45.5:80)
Connecting to www.linux.com (151.101.45.5:443)
wget: can't open 'index.html': Permission denied
/ $ exit
9. Make sure traffic is being sent to the correct Pod. Check the details of both the service and endpoint. Pay close attention
to ports in use as a simple typo can prevent traffic from reaching the proper pod. Make sure labels and selectors don’t
have any typos as well.
secondapp LoadBalancer 10.109.26.21 <pending> 80:32000/TCP 1d
thirdpage NodePort 10.109.250.78 <none> 80:31230/TCP 1h
student@ckad-1:~$ kubectl get svc secondapp -o yaml
<output_omitted>
clusterIP: 10.109.26.21
externalTrafficPolicy: Cluster
ports:
- nodePort: 32000
port: 80
protocol: TCP
targetPort: 80
selector:
example: second
<output_omitted>
10. Verify an endpoint for the service exists and has expected values, including namespaces, ports and protocols.
student@ckad-1:~$ kubectl get ep
NAME ENDPOINTS AGE
kubernetes 10.128.0.3:6443 10d
nginx 192.168.55.68:443 10d
registry 192.168.55.69:5000 10d
secondapp 192.168.55.91:80 1d
thirdpage 192.168.241.57:80 1h
student@ckad-1:~$ kubectl get ep secondapp -o yaml
apiVersion: v1
kind: Endpoints
metadata:
<output_omitted>
11. If the containers, services and endpoints are working the issue may be with an infrastructure service like kube-proxy.
Ensure it’s running, then look for errors in the logs. As we have two nodes we will have two proxies to look at. As we
built our cluster with kubeadm the proxy runs as a container. On other systems you may need to use journalctl or look
under /var/log/kube-proxy.log.
student@ckad-1:~$ ps -elf |grep kube-proxy
4 S root 2864 2847 0 80 0 - 14178 - 15:45 ?
00:00:56 /usr/local/bin/kube-proxy --config=/var/lib/kube-proxy/config.conf
0 S student 23513 18282 0 80 0 - 3236 pipe_w 22:49 pts/0
00:00:00 grep --color=auto kube-proxy
student@ckad-1:~$ journalctl -a | grep proxy
Apr 15 15:44:43 ckad-2-nzjr audit[742]: AVC apparmor="STATUS"
operation="profile_load" profile="unconfined" \
name="/usr/lib/lxd/lxd-bridge-proxy" pid=742 comm="apparmor_parser"
Apr 15 15:44:43 ckad-2-nzjr kernel: audit: type=1400
audit(1523807083.011:11): apparmor="STATUS" \
operation="profile_load" profile="unconfined" \
name="/usr/lib/lxd/lxd-bridge-proxy" pid=742 comm="apparmor_parser"
Apr 15 15:45:17 ckad-2-nzjr kubelet[1248]: I0415 15:45:17.153670
1248 reconciler.go:217] operationExecutor.VerifyControllerAttachedVolume\
started for volume "xtables-lock" \
(UniqueName: "kubernetes.io/host-path/e701fc01-38f3-11e8-a142-\
42010a800003-xtables-lock") \
pod "kube-proxy-t8k4w" (UID: "e701fc01-38f3-11e8-a142-42010a800003")
12. Look at both of the proxy logs. Lines which begin with the character I are info, E are errors. In this example the last
message says access to listing an endpoint was denied by RBAC. It was because a default installation via Helm wasn’t
RBAC aware. If not using command line completion, view the possible pod names first.
student@ckad-1:~$ kubectl -n kube-system get pod
student@ckad-1:~$ kubectl -n kube-system logs kube-proxy-fsdfr

I0405 17:28:37.091224 1 feature_gate.go:190] feature gates: map[]
W0405 17:28:37.100565 1 server_others.go:289] Flag proxy-mode=""
unknown, assuming iptables proxy
I0405 17:28:37.101846 1 server_others.go:138] Using iptables Proxier.
I0405 17:28:37.121601 1 server_others.go:171] Tearing down
inactive rules.
<output_omitted>
E0415 15:45:17.086081 1 reflector.go:205] \
k8s.io/kubernetes/pkg/client/informers/informers_generated/
internalversion/factory.go:85: \
Failed to list *core.Endpoints: endpoints is forbidden: \
User "system:serviceaccount:kube-system:kube-proxy" cannot \
list endpoints at the cluster scope:\
[clusterrole.rbac.authorization.k8s.io "system:node-proxier" not found, \
clusterrole.rbac.authorization.k8s.io "system:basic-user" not found,
clusterrole.rbac.authorization.k8s.io \
"system:discovery" not found]
13. Check that the proxy is creating the expected rules for the problem service. Find the destination port being used for the
service, 30195 in this case.
student@ckad-1:~$ sudo iptables-save |grep secondapp
79
-A KUBE-NODEPORTS -p tcp -m comment --comment "default/secondapp:" \

-m tcp --dport 30195 -j KUBE-MARK-MASQ
-A KUBE-NODEPORTS -p tcp -m comment --comment "default/secondapp:" \
-m tcp --dport 30195 -j KUBE-SVC-DAASHM5XQZF5XI3E
-A KUBE-SEP-YDKKGXN54FN2TFPE -s 192.168.55.91/32 -m comment --comment \
"default/secondapp:" -j KUBE-MARK-MASQ
-A KUBE-SEP-YDKKGXN54FN2TFPE -p tcp -m comment --comment "default/secondapp:"\
-m tcp -j DNAT --to-destination 192.168.55.91:80
-A KUBE-SERVICES ! -s 192.168.0.0/16 -d 10.109.26.21/32 -p tcp \
-m comment --comment "default/secondapp: \
cluster IP" -m tcp --dport 80 -j KUBE-MARK-MASQ
-A KUBE-SERVICES -d 10.109.26.21/32 -p tcp -m comment --comment \
"default/secondapp: cluster IP" -m tcp --dport 80 -j KUBE-SVC-DAASHM5XQZF5XI3E
-A KUBE-SVC-DAASHM5XQZF5XI3E -m comment --comment "default/secondapp:" \
<output_omitted>
14. Ensure the proxy is working by checking the port targeted by iptables. If it fails open a second terminal and view the
proxy logs when making a request as it happens.
student@ckad-1:~$ curl localhost:32000
<!DOCTYPE html>
<html>
<head>
<output_omitted>
Exercise 8.2: Conformance Testing
The cncf.io group is in the process of formalizing what is considered to be a conforming Kubernetes cluster. While that
project matures there is an existing tool provided by Heptio which can be useful. We will need to make sure a newer
version of Golang is installed for it to work. You can download the code from github and look around with git or with go,
depending on which tool you are most familiar.
1. Create a new directory to hold the testing code.

student@ckad-1:~$ mkdir test
student@ckad-1:~$ cd test/
2. Use git to download the sonobuoy code. View the resource after it downloads.
student@ckad-1:~/test$ git clone https://github.com/heptio/sonobuoy
Cloning into 'sonobuoy'...
remote: Counting objects: 7847, done.
remote: Compressing objects: 100% (23/23), done.
remote: Total 7847 (delta 2), reused 0 (delta 0), pack-reused 7824
Receiving objects: 100% (7847/7847), 10.19 MiB | 0 bytes/s, done.
Resolving deltas: 100% (3818/3818), done.
Checking connectivity... done.
student@ckad-1:~/test$ ls
sonobuoy
student@ckad-1:~/test$ cd sonobuoy/
student@ckad-1:~/test/sonobuoy$ ls
cmd Gopkg.toml scripts
CODE_OF_CONDUCT.md heptio-images-ee4b0474b93e.json.enc SUPPORT.md
CONTRIBUTING.md LICENSE test
Dockerfile main.go travis-deploy.sh
docs Makefile vendor
examples pkg
Gopkg.lock README.md
student@ckad-1:~/test/sonobuoy$ less README.md
3. The Heptio team suggests the use of an easy to use Golang tool gimme. We will follow their suggestion and use it to
pull their code. Start by making sure you have a bin directory under your home directory.
student@ckad-1:~/test/sonobuoy$ cd ; mkdir ~/bin
4. Use curl to download the binary. Note the use of -o as in output to save the binary to the newly created directory.
student@ckad-1:~$ curl -sL -o ~/bin/gimme
https://raw.githubusercontent.com/travis-ci/gimme/master/gimme
5. View the file. Note it is not yet executable. Make it so.

student@ckad-1:~$ ls -l ~/bin/gimme
-rw-rw-r-- 1 student student 27035 Apr 15 20:46 /home/student/bin/gimme
student@ckad-1:~$ chmod +x ~/bin/gimme
6. Use the gimme tool to download the stable version of Go.

student@ckad-1:~$ ~/bin/gimme stable
unset GOOS;
unset GOARCH;
export GOROOT='/home/student/.gimme/versions/go1.10.1.linux.amd64';
export PATH="/home/student/.gimme/versions/go1.10.1.linux.amd64/bin:$PATH";
go version >&2;
export GIMME_ENV="/home/student/.gimme/envs/go1.10.1.env"
7. Ensure the expected path has been set and exported. You can copy the second from the previous output.
student@ckad-1:~$ export PATH=$GOROOT/bin:$GOPATH/bin:$PATH
student@ckad-1:~$ export PATH="/home/student/.gimme/versions/go1.10.1.linux.amd64/bin:$PATH"
student@ckad-1:~$ export GOPATH=$PATH
8. Use the go command to download the sonobuoy code. You may need to install the software package, golang-go, if it
is not already installed.
student@ckad-1:~$ go get -u -v github.com/heptio/sonobuoy
github.com/heptio/sonobuoy (download)
created GOPATH=/home/student/go; see 'go help gopath'
github.com/heptio/sonobuoy/pkg/buildinfo
<output_omitted>
9. Execute the newly downloaded tool with the run option. Review the output. Take note of interesting tests in order to
search for particular output in the logs. The binary has moved over time, so you may need to use the find command to
locate it. The long path wraps, but you would type the command as one line.
student@ckad-1:~/test/sonobuoy$
~/.gimme/versions/go1.10.3.linux.amd64/bin/bin/sonobuoy run
Running plugins: e2e, systemd-logs
INFO[0000] created object name=heptio-sonobuoy namespace= resource=na....
INFO[0000] created object name=sonobuoy-serviceaccount namespace=hept....
INFO[0000] created object name=sonobuoy-serviceaccount-heptio-sonobuo...
INFO[0000] created object name=sonobuoy-serviceaccount namespace= res....
INFO[0000] created object name=sonobuoy-config-cm namespace=heptio-....
INFO[0000] created object name=sonobuoy-plugins-cm namespace=hepti....
10. Check the status of sonobuoy. It can take up to an hour to finish on large clusters. On our two-node cluster it will take
about two minutes. The path is long so is presented on the line after the prompt.
student@ckad-1:~/test/sonobuoy$
81
~/.gimme/versions/go1.10.3.linux.amd64/bin/bin/sonobuoy status
PLUGIN STATUS COUNT

e2e running 1
systemd_logs complete 2
Sonobuoy is still running. Runs can take up to 60 minutes.
11. Look at the logs. If the tests are ongoing you will see incomplete logs.
student@ckad-1:~/test/sonobuoy$ ~/.gimme/versions/go1.10.3.linux.amd64/bin/bin/sonobuoy logs
namespace="heptio-sonobuoy" pod="sonobuoy-systemd-logs-daemon-set-\
e322ef32b0804cd2-d48np" container="sonobuoy-worker"
time="2018-04-15T20:50:48Z" level=info msg="Waiting for waitfile" \
waitfile=/tmp/results/done
time="2018-04-15T20:50:49Z" level=info msg="Detected done file, \
transmitting result file"
<output_omitted>
12. Change into the client directory and look at the tests and results generated.
student@ckad-1:~/test/sonobuoy$ cd /home/student/test/sonobuoy/pkg/client/
student@ckad-1:~/test/sonobuoy/pkg/client$ ls
defaults.go doc.go example_interfaces_test.go gen_test.go logs.go mode.go results\
run.go
delete.go e2e.go gen.go interfaces.go logs_test.go preflight.go retrieve.go\
status.go
student@ckad-1:~/test/sonobuoy/pkg/client$ cd results/
student@ckad-1:~/test/sonobuoy/pkg/client/results$ ls
doc.go e2e junit_utils.go reader.go reader_test.go
testdata types.go
student@ckad-1:~/test/sonobuoy/pkg/client/results$ cd testdata/
student@ckad-1:~/test/sonobuoy/pkg/client/results/testdata$ ls -l
total 644
-rw-rw-r-- 1 student student 407010 Apr 15 20:43 results-0.10.tar.gz
student@ckad-1:~/test/sonobuoy/pkg/client/results/testdata$ tar -xf results-0.8.tar.gz
student@ckad-1:~/test/sonobuoy/pkg/client/results/testdata$ ls
config.json hosts plugins resources results-0.10.tar.gz
results-0.8.tar.gz results-0.9.tar.gz serverversion
student@ckad-1:~/test/sonobuoy/pkg/client/results/testdata$ less
plugins/e2e/results/e2e.log
Dec 13 17:06:53.480: INFO: Overriding default scale value of zero to 1
Dec 13 17:06:53.481: INFO: Overriding default milliseconds value of ....
Running Suite: Kubernetes e2e suite
===================================
Random Seed: 1513184813 - Will randomize all specs
Will run 1 of 698 specs
Dec 13 17:06:54.705: INFO: >>> kubeConfig:

Dec 13 17:06:54.707: INFO: Waiting up to 4h0m0s for all (but 0) nodes...
Dec 13 17:06:54.735: INFO: Waiting up to 10m0s for all pods (need at
namespace 'kube-system' to be running a
nd ready
Dec 13 17:06:54.895: INFO: 14 / 14 pods in namespace 'kube-system'
are running and ready (0 seconds elapsed)
Dec 13 17:06:54.895: INFO: expected 3 pod replicas in namespace
'kube-system', 3 are Running and Ready.
<output_omitted>
13. Find other files which have been generated, and their size.
student@ckad-1:~/t..../testdata$ find .
.
./results-0.8.tar.gz
./results-0.10.tar.gz
./hosts
./hosts/ip-10-0-9-16.us-west-2.compute.internal
<output_omitted>
14. Continue to look through tests and results as time permits. There is also an online, graphical scanner. In testing inside
GCE the results were blocked and never returned. You may have different outcome in other environments.

LFD259 Labs - V2019 01 14

Uploaded by

Copyright:

Available Formats

LFD259 Labs - V2019 01 14

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

LFD259 Labs - V2019 01 14

Uploaded by

Copyright:

Available Formats

What is Kubernetes architecture?

What is Kubernetes architecture?

What are the components of Kubernetes?

What are the components of Kubernetes?

LFD259

LFD259: Version 2019-01-14

© Copyright the Linux Foundation 2019. All rights reserved.

© Copyright the Linux Foundation 2019. All rights reserved.

the Linux Foundation

Exercise 2.1: Overview and Preliminaries

Download shell scripts and YAML files

student@ckad-1:~$ tar -xvf lfd259-example-file.1-13-1.tar

Exercise 2.2: Deploy a New Cluster

Deploy a Master Node using Kubeadm

echo "Update the local node"

sudo apt-get install -y docker.io

sudo sh -c "curl -s https://packages.cloud.google.com/apt/doc/apt-key.gpg | apt-key add -"

sudo apt-get update

sudo apt-get install -y kubeadm=1.13.1-00 kubelet=1.13.1-00 kubectl=1.13.1-00

## If you are going to use a different plugin you'll want

sudo kubeadm init --kubernetes-version 1.13.1 --pod-network-cidr 192.168.0.0/16

sudo cp -i /etc/kubernetes/admin.conf $HOME/.kube/config

sudo chown $(id -u):$(id -g) $HOME/.kube/config

wget https://tinyurl.com/yb4xturm -O rbac-kdd.yaml

wget https://tinyurl.com/y8lvqc9g -O calico.yaml

kubectl apply -f rbac-kdd.yaml

kubectl apply -f calico.yaml

Your Kubernetes master has initialized successfully!

To start using your cluster, you need to run the

You should now deploy a pod network to the cluster.

You can now join any number of machines by running the

kubeadm join 10.128.0.3:6443 --token 69rdjq.2x20l2j9ncexy37b

+ kubectl get node

Script finished. Move to the next step

Deploy a Minion Node

echo " Update the local node"

echo " Install Docker"

sudo sh -c "curl -s https://packages.cloud.google.com/apt/doc/apt-key.gpg | apt-key add -"

sudo apt-get update

sudo apt-get install -y kubeadm=1.13.1-00 kubelet=1.13.1-00 kubectl=1.13.1-00

4. Run the script on the second node.

student@ckad-2:~$ sudo kubeadm join --token 118c3e.83b49999dc5dc034 \

Configure the Master Node

student@ckad-1:~$ echo "source <(kubectl completion bash)" >> ~/.bashrc

Find more information at:

Basic Commands (Beginner):

Basic Commands (Intermediate):

* A taint consists of a key, value, and effect. As an argument

Exercise 2.3: Create a Basic Pod

student@ckad-1:~$ kubectl create -f basic.yaml

5. Shut down the pod and verify it is no longer running.

student@ckad-1:~$ kubectl delete pod basicpod

student@ckad-1:~$ vim basic.yaml

Exercise 2.4: Multi-Container Pods

Exercise 2.5: Create a Simple Deployment

student@ckad-1:~$ kubectl get deployment,pod

NAME READY STATUS RESTARTS AGE

student@ckad-1:~$ kubectl describe pod firstpod-6bb4574d94-rqk76

NAME DESIRED CURRENT READY....