Get your Java Microservice up and running...
Exercise 3: Deploy to the Kubernetes

In this exercise we will work in the Kubernetes Web Console and with the Kubernetes CLI.
​"Kubernetes (K8s) is an open-source system for automating deployment, scaling, and management of containerized applications."​
The following image is a simplified overview of the topics of that lab.
overview
This lab has two parts:
Start build and save the container image
Deploy the application and expose the service
We will define and apply a deployment configuration (yaml) to create a Pod with our Microservice
We will define a service which routes requests to the Pod with our Microservice
The following gif is an animation of the simplified steps above in a sequence.
overview
Step 1: Ensure you have the terminal session open with the started Docker image and you have downloaded the Cloud Native Starter project also in this running container
Step 2:  Navigate to the folder cloud-native-starter/authors-java-jee
Note: You have cloned the project twice: first to your local machine and second into the Docker image. The code changes you did in execrise 2 on your local computer, don't exist in the running Docker container.
1. Build and save the container image
Step 1: Build and save the container image in the IBM Cloud Container Registry
Now we want to build and save a container image in the IBM Cloud Container Registry.
Ensure you logon on to IBM Cloud.
REMEMBER: You should know this from the prerequisites.
You can follow the steps in the Access tab, by starting from After your cluster provision .. and inserting the commands into your terminal session.
​​
Logon to the IBM Cloud Container Registry (Ensure you are in the $ROOT_FOLDER/authors-java-jee)
 cd $ROOT_FOLDER/authors-java-jee
 ibmcloud cr login
List you namespaces inside the IBM Cloud Container Registry
 ibmcloud cr namespaces
Example output:
 $ Listing namespaces for account 'Thomas Suedbroecker's Account' in registry 'us.icr.io'...
 $
 $ Namespace
 $ cloud-native-suedbro
Now upload the code and build the container image inside IBM Cloud Container Registry. We use the information from step 3, where we got the list of namespaces.
 ibmcloud cr build -f Dockerfile --tag [YOUR_REGISTRY]/[YOUR_REGISTRY_NAMESPACE]/authors:1 .
Example command:
[YOUR_REGISTRY] = us.icr.io
[YOUR_REGISTRY_NAMESPACE] = cloud-native-suedbro
ibmcloud cr build -f Dockerfile --tag us.icr.io/cloud-native-suedbro/authors:1 .
Optional: Verify the container upload in the IBM Cloud web UI.
​​
List the container images to verify the upload.
 ibmcloud cr images
Example output:
 $ Listing images...
 $
 $ Repository                               Tag   Digest         Namespace              Created         Size     Security status
 $ us.icr.io/cloud-native-suedbro/authors   1     5a86758f1056   cloud-native-suedbro   2 minutes ago   226 MB   3 Issues
 $
 $ OK
Copy the REPOSITORY path for the uploaded Authors container image. In this sample case it would be: us.icr.io/cloud-native-suedbro/authors and save it somewhere, we need this later in the deployment.yaml configuration.
2. Apply the Deployment
This deployment will deploy a container to a Pod in Kubernetes. For more details we use the Kubernetes documentation for Pods.
A Pod is the basic building block of Kubernetes-the smallest and simplest unit in the Kubernetes object model that you create or deploy. A Pod represents processes running on your Cluster .
Here is a simplified image for that topic. The deployment.yaml file points to the container image that needs to be instantiated in the pod.
deployment
Inside the container image cns-workshop-tools you can use the editor nano.
nano deployment.yaml
Let's start with the deployment yaml. For more details see the Kubernetes documentation for deployments.
Definition of kind defines this as a Deployment configuration.
  kind: Deployment
  apiVersion: apps/v1
  metadata:
    name: authors
In the spec section we specify an app name and version label.
  spec:
    ...
    template:
      metadata:
        labels:
          app: authors
          version: v1
Then we define a name for the container and we provide the container image location, e.g. where the container can be found in the Container Registry.
The containerPort depends on the port definition inside our Dockerfile and in our server.xml.
We have previously talked about the usage of the HealthEndpoint class for our Authors service and here we see it the livenessProbe definition.
  spec:
        containers:
        - name: authors
          image: authors:1
          ports:
          - containerPort: 3000
          livenessProbe:
This is the full deployment.yaml file.
  kind: Deployment
  apiVersion: apps/v1
  metadata:
    name: authors
  spec:
    selector:
    matchLabels:
      app: authors
      version: v1
    replicas: 1
    template:
      metadata:
        labels:
          app: authors
          version: v1
      spec:
        containers:
        - name: authors
          image: us.icr.io/cloud-native-suedbro/authors:1
          ports:
          - containerPort: 3000
          livenessProbe:
            exec:
              command: ["sh", "-c", "curl -s http://localhost:3000/"]
            initialDelaySeconds: 20
          readinessProbe:
            exec:
              command: ["sh", "-c", "curl -s http://localhost:3000/health | grep -q authors"]
            initialDelaySeconds: 40
        restartPolicy: Always
Step 1: Apply the deployment
Ensure you are in the $ROOT_FOLDER/authors-java-jee/deployment
cd $ROOT_FOLDER/authors-java-jee/deployment
Open the ../authors-java-jee/deployment/deployment.yaml file with a editor and replace the value for the container image location with the path we got from the IBM Container Registry and just replace the authors:1 text, and add following statement imagePullPolicy: Always and save the file.
Note: With the specification imagePullPolicy: Always we force that the image is pulled from the IBM Cloud Container Registry and not cashed image in Kubernetes is possible used, when we change our container image IBM Cloud Container Registry.
REMEMBER: You should have saved the IBM Container Registry information somewhere.
Before:
    image: authors:1
Sample change:
    image: us.icr.io/cloud-native-suedbro/authors:1
    imagePullPolicy: Always
    ports:
        - containerPort: 3000
Now we apply the deployment and we create a new Authors Pod.
 kubectl apply -f deployment.yaml
Step 2: Verify the deployment with kubectl
Insert this command and verify the output.
 kubectl get pods
Sample output:
 NAME                      READY   STATUS    RESTARTS   AGE
 authors-7b6dd98db-wl9wc   1/1     Running   0          6m9s
Step 3: Verify the deployment with the Kubernetes dashboard
Open your Kubernetes Cluster in the IBM Cloud web console
Open the Kubernetes dashbord
​​
In the overview you see the created deployment and the pod
​​
3. Apply the service
After the definition of the Pod we need to define how to access the Pod. For this we use a service in Kubernetes. For more details see the Kubernetes documentation for service.
A Kubernetes Service is an abstraction which defines a logical set of Pods and a policy by which to access them - sometimes called a micro-service. The set of Pods targeted by a Service is (usually) determined by a Label Selector.
In the service we map the NodePort of the cluster to the port 3000 of the Authors Microservice running in the authors Pod, as we can see in the following picture.
service
In the service.yaml we see a selector of the pod using the label 'app: authors'.
kind: Service
apiVersion: v1
metadata:
  name: authors
  labels:
    app: authors
spec:
  selector:
    app: authors
  ports:
    - port: 3000
      name: http
  type: NodePort
---
Step 1: Ensure you are in the $ROOT_FOLDER/authors-java-jee/deployment
  cd $ROOT_FOLDER/authors-java-jee/deployment
Step 2: Apply the service specification
  kubectl apply -f service.yaml
Step 3: Verify the service in Kubernetes with kubectl
  kubectl get services
Sample output:
  NAME         TYPE        CLUSTER-IP       EXTERNAL-IP   PORT(S)          AGE
  authors      NodePort    172.21.107.135   <none>        3000:31347/TCP   22s
  kubernetes   ClusterIP   172.21.0.1       <none>        443/TCP          28h
Step 4: Verify the service in the Kubernetes dashboard
Open your Kubernetes Cluster in the IBM Cloud web console
Open the Kubernetes dashbord
​​
In the overview scroll down until you see the created service
​​
Step 5: Verify the running Microservice on Kubernetes
Get cluster (worker node) IP address and show the IP address
 clusterip=$(ibmcloud ks workers --cluster cloud-native | awk '/Ready/ {print $2;exit;}')
 echo $clusterip
Example output:
 184.172.247.228
Expose a public port on your worker node and use the public IP address of the worker node to access your service in the cluster publicly from the internet.
Get nodeport to access the service (do you remember the mapping?)
 nodeport=$(kubectl get svc authors --ignore-not-found --output 'jsonpath={.spec.ports[*].nodePort}')
 echo $nodeport
Example output:
 31347
Open API explorer.
 echo http://${clusterip}:${nodeport}/openapi/ui/
Sample output:
 http://184.172.247.228:31347/openapi/ui/
Copy and past the URL in a local browser on your PC:
​​
Execute curl to test the Authors service.
 curl http://${clusterip}:${nodeport}/api/v1/getauthor?name=Niklas%20Heidloff
Example output:
 {"name":"Niklas Heidloff","twitter":"@nheidloff","blog":"http://heidloff.net"}
Execute following curl command to test the HealthCheck implementation for the Authors service.
curl http://${clusterip}:${nodeport}/health
Example output:
{"checks":[{"data":{"authors":"ok"},"name":"authors","state":"UP"}],"outcome":"UP"}
Optional:
We can also verify that call in the browser.
​​
We can simply delete the deployed Authors Microservice with:
kubectl delete pods,services -l app=authors
Congratulations you have finished this hands-on workshop. Maybe you want to verify your learning in the Cloud Native Starter Level 1 Badge.