I wanted a helm chart of Googles microservices demo to deploy and maintain the deployment using helm. That's it.
Get yourself a copy of the repo: [email protected]:ronamosa/hipstershop-demo.git, and follow the instructions below, depending on your intended setup.
Ubuntu:
sudo snap install microk8s --classic
microk8s.statusenable helm version 3
microk8s.enable helm3TBC
Do a dry-run first before you deploy to make sure the charts are happy.
The cli convention here is: helm-command 'install|upgrade --install' '--debug --dry-run' <helm release name> <chart-folder>
microk8s.helm3 install --debug --dry-run hipstershop helm/Now, deploy it
microk8s.helm3 install --debug hipstershop helm/Check the release
microk8s.helm3 list
NAME NAMESPACE REVISION UPDATED STATUS CHART APP VERSION
hipstershop default 1 2020-07-15 19:25:45.695583276 +1200 NZST deployed hipstershop-0.1.0 1.16.0 Enable istio in microK8s:
microk8s.enable istioEnable side-car injection on the namespace where helm chart will be deployed e.g. 'default'
microk8s.kubectl label namespace default istio-injection=enabledDeploy helm chart
microk8s.helm3 install --debug hipstershop helm/Check the release
microk8s.helm3 list
NAME NAMESPACE REVISION UPDATED STATUS CHART APP VERSION
hipstershop default 1 2020-07-15 19:25:45.695583276 +1200 NZST deployed hipstershop-0.1.0 1.16.0 Check the deployment for Istio side-cars, each pod should have a READY column with '2/2'
microk8s.kubectl get po
NAME READY STATUS RESTARTS AGE
adservice-59bd9cb647-9z28b 2/2 Running 0 114s
cartservice-6d4ccdfd5-qhbfl 2/2 Running 3 114s
checkoutservice-56cd667bbb-fq4xt 2/2 Running 0 113s
currencyservice-6cb45fbff5-l4xsj 2/2 Running 0 114s
emailservice-75c874fb64-fxlzw 2/2 Running 0 114s
frontend-5444bd96ff-6glnb 2/2 Running 1 114s
loadgenerator-7cb5886b74-wj4hf 2/2 Running 4 113s
paymentservice-6586f9667d-drq5n 2/2 Running 0 114s
productcatalogservice-565d4975cd-8mkcl 2/2 Running 0 114s
recommendationservice-596bbccd5d-cpjz4 2/2 Running 0 114s
redis-cart-8465c75f49-kr76p 2/2 Running 0 113s
shippingservice-6ccbc78688-mfz46 2/2 Running 0 114sCheck Istio proxy status
microk8s.istioctl ps
NAME CDS LDS EDS RDS PILOT VERSION
adservice-59bd9cb647-9z28b.default SYNCED SYNCED SYNCED SYNCED istio-pilot-856b6b9b8f-p97pc 1.5.1
cartservice-6d4ccdfd5-qhbfl.default SYNCED SYNCED SYNCED SYNCED istio-pilot-856b6b9b8f-p97pc 1.5.1
checkoutservice-56cd667bbb-fq4xt.default SYNCED SYNCED SYNCED SYNCED istio-pilot-856b6b9b8f-p97pc 1.5.1
currencyservice-6cb45fbff5-l4xsj.default SYNCED SYNCED SYNCED SYNCED istio-pilot-856b6b9b8f-p97pc 1.5.1
emailservice-75c874fb64-fxlzw.default SYNCED SYNCED SYNCED SYNCED istio-pilot-856b6b9b8f-p97pc 1.5.1
frontend-5444bd96ff-6glnb.default SYNCED SYNCED SYNCED SYNCED istio-pilot-856b6b9b8f-p97pc 1.5.1
istio-egressgateway-79b99bfc6b-lrj5d.istio-system SYNCED SYNCED SYNCED NOT SENT istio-pilot-856b6b9b8f-p97pc 1.5.1
istio-ingressgateway-696d6f46f5-48h4g.istio-system SYNCED SYNCED SYNCED SYNCED istio-pilot-856b6b9b8f-p97pc 1.5.1
loadgenerator-7cb5886b74-wj4hf.default SYNCED SYNCED SYNCED SYNCED istio-pilot-856b6b9b8f-p97pc 1.5.1
paymentservice-6586f9667d-drq5n.default SYNCED SYNCED SYNCED SYNCED istio-pilot-856b6b9b8f-p97pc 1.5.1
productcatalogservice-565d4975cd-8mkcl.default SYNCED SYNCED SYNCED SYNCED istio-pilot-856b6b9b8f-p97pc 1.5.1
recommendationservice-596bbccd5d-cpjz4.default SYNCED SYNCED SYNCED SYNCED istio-pilot-856b6b9b8f-p97pc 1.5.1
redis-cart-8465c75f49-kr76p.default SYNCED SYNCED SYNCED SYNCED istio-pilot-856b6b9b8f-p97pc 1.5.1
shippingservice-6ccbc78688-mfz46.default SYNCED SYNCED SYNCED SYNCED istio-pilot-856b6b9b8f-p97pc 1.5.1If your deploy went without error you should be able to run these commands and see the IP addressses of the services you deployed:
for example
microk8s.kubectl get svc
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
adservice ClusterIP 10.152.183.33 <none> 9555/TCP 4m
cartservice ClusterIP 10.152.183.34 <none> 7070/TCP 4m
checkoutservice ClusterIP 10.152.183.190 <none> 5050/TCP 4m
currencyservice ClusterIP 10.152.183.243 <none> 7000/TCP 4m
emailservice ClusterIP 10.152.183.76 <none> 5000/TCP 4m
frontend ClusterIP 10.152.183.39 <none> 80/TCP 4m
frontend-external LoadBalancer 10.152.183.140 <pending> 80:31446/TCP 4m
kubernetes ClusterIP 10.152.183.1 <none> 443/TCP 16d
paymentservice ClusterIP 10.152.183.137 <none> 50051/TCP 4m
productcatalogservice ClusterIP 10.152.183.27 <none> 3550/TCP 4m
recommendationservice ClusterIP 10.152.183.70 <none> 8080/TCP 4m
redis-cart ClusterIP 10.152.183.107 <none> 6379/TCP 4m
shippingservice ClusterIP 10.152.183.47 <none> 50051/TCP 4mOpen your browser to http://10.152.183.39 (frontend) or http://10.152.183.140 (frontend-external)
If you want to expose your shop deployment to your LAN (the network your PC is on) use the following command to patch the frontend-external service to your machines IP address
kubectl patch svc frontend-external -n hipster-shop -p '{"spec": {"type": "LoadBalancer", "externalIPs":["<ip-address of masternode>"]}}'
for example, have look at your k8s services
$ microk8s.kubectl get svc
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
adservice ClusterIP 10.152.183.183 <none> 9555/TCP 3h26m
cartservice ClusterIP 10.152.183.238 <none> 7070/TCP 3h26m
checkoutservice ClusterIP 10.152.183.124 <none> 5050/TCP 3h26m
currencyservice ClusterIP 10.152.183.247 <none> 7000/TCP 3h26m
emailservice ClusterIP 10.152.183.90 <none> 5000/TCP 3h26m
frontend ClusterIP 10.152.183.13 <none> 80/TCP 3h26m
frontend-external LoadBalancer 10.152.183.172 <pending> 80:30829/TCP 3h26m
kubernetes ClusterIP 10.152.183.1 <none> 443/TCP 11d
paymentservice ClusterIP 10.152.183.207 <none> 50051/TCP 3h26m
productcatalogservice ClusterIP 10.152.183.22 <none> 3550/TCP 3h26m
recommendationservice ClusterIP 10.152.183.165 <none> 8080/TCP 3h26m
redis-cart ClusterIP 10.152.183.8 <none> 6379/TCP 3h26m
shippingservice ClusterIP 10.152.183.46 <none> 50051/TCP 3h26mget your computers IP address (e.g. 192.168.1.11)
run the patch: microk8s.kubectl patch svc frontend-external -p '{"spec": {"type": "LoadBalancer", "externalIPs":["192.168.1.11"]}}'
check out your k8s services again
$ microk8s.kubectl get svc
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
adservice ClusterIP 10.152.183.183 <none> 9555/TCP 6h45m
cartservice ClusterIP 10.152.183.238 <none> 7070/TCP 6h45m
checkoutservice ClusterIP 10.152.183.124 <none> 5050/TCP 6h45m
currencyservice ClusterIP 10.152.183.247 <none> 7000/TCP 6h45m
emailservice ClusterIP 10.152.183.90 <none> 5000/TCP 6h45m
frontend ClusterIP 10.152.183.13 <none> 80/TCP 6h45m
frontend-external LoadBalancer 10.152.183.172 192.168.1.11 80:30829/TCP 6h45m
kubernetes ClusterIP 10.152.183.1 <none> 443/TCP 11d
paymentservice ClusterIP 10.152.183.207 <none> 50051/TCP 6h45m
productcatalogservice ClusterIP 10.152.183.22 <none> 3550/TCP 6h45m
recommendationservice ClusterIP 10.152.183.165 <none> 8080/TCP 6h45m
redis-cart ClusterIP 10.152.183.8 <none> 6379/TCP 6h45m
shippingservice ClusterIP 10.152.183.46 <none> 50051/TCP 6h45mNow, open http://192.168.1.11:30829 and you will see the hipster shop.
If you see the recommendationservice pod 'CrashLooping', check the logs and if they are talking about 'GOOGLE_APPLICATION_CREDENTIALS' being missing you have two choices:
- Get your creds from your GCP account, save them as a .json file, and then run
'export GOOGLE_APPLICATION_CREDENTIALS=/path/to/json/file', and now your stackdriver should be ok. - Disable the functions in the microservice that needs stackdriver
make sure your 'recommendationservice/templates/deployment.yaml' has these uncommented
- name: DISABLE_TRACING
value: "1"
- name: DISABLE_PROFILER
value: "1"
- name: DISABLE_DEBUGGER
value: "1"Uninstallation is really easy with helm, run this command and watch (only if you want to) the pods terminate and everything deployed by helm will be removed (remember the release name for the example is 'hipstershop'):
microk8s.helm3 delete hipstershopRon Amosa ([email protected])