In this hands-on lab we will be looking at using Helm to deploy a microservice stack in our Minikube cluster. We will be using the Instana robot-shop application as an example.
Learning Objectives
Successfully complete this lab by achieving the following learning objectives:
- Start the Minikube Cluster Using the Correct Driver
Issue the command to start Minikube
sudo minikube start --vm-driver none- Unpack Helm, Move it into the Path, Install Socat and Run helm init
Unpack the
helm.tar.gzfile that is sitting in our home directory:tar -xvzf ~/helm.tar.gzMove the
helmandtillerexecutables into the path at/usr/local/bin:sudo mv ./linux-amd64/helm /usr/local/bin sudo mv ./linux-amd64/tiller /usr/local/binTo test, run
helm versionfrom our home directory. This means it’s in our path and we can runhelmcommands from anywhere.Initialize Helm:
sudo helm initCheck that
helmandtillerare up and available:sudo helm versionHelm requires socat in order to run, but it is already installed on your lab server.
- Install the Robot-Shop Application into Its Own Namespace via Helm
Get into the directory containing the Helm chart:
cd ~/robot-shop/K8s/helmCreate the name space:
sudo kubectl create namespace robot-shopRun the Helm installation:
sudo helm install --name robot-shop --namespace robot-shop .Verify that the pods are running:
sudo kubectl -n robot-shop get poIt might take a couple of minutes for all the pods to stand up.
- Edit the Web Service to Use Nodeport and Configure Nginx to Proxy to the Web Service
Edit the web service:
sudo kubectl -n robot-shop edit service webEdit the service spec similar to this (changing
LoadBalancertoNodePort):selector: service: web sessionAffinity: None type: NodePortMake sure our change took effect:
sudo kubectl -n robot-shop get service webGet the target port from Minikube:
sudo minikube service listPay attention to TARGET PORT on web. We’ll need that in a minute.
Configure Nginx to proxy to the target port from service list. Get the file open for editing:
sudo vim /etc/nginx/sites-enabled/defaultNow, down at about line 50, we’ve got to change something in the
locationsection. We’ll paste that TARGET PORT we saw earlier in here, replacing the existing line with what’s shown here (theproxy_passline):location / { # First attempt to serve request as file, then # as directory, then fall back to displaying a 404. proxy_pass http://<minikube IP>:<svc port>;Our changes should take effect after an Nginx restart:
sudo systemctl restart nginxOpen a browser and point it to our server’s public IP address to ensure the application is running.
