Istio Webinar Postmortem
![image](https://a.storyblok.com/f/153547/768x576/26fc0d0604/istio-blog-image-768x576.png)
$ kubectl apply -f flaskapp-deployment.yamlWhat gives? This deployment spec has worked reliably time and time again with no business failing to pull the image. I can only guess that Docker Hub is down (unlikely) and had two options to choose from: 1) re-build the image from source, or 2) Use a backup environment to show the end state. In order to keep on topic within the given time period, I decided to go with option #2 to at least showcase Istio Ingress at its best.
$ kubectl get pods
NAME READY STATUS
flaskapp-deployment-pod-1 0/1 ImagePullBackOff
flaskapp-deployment-pod-2 0/1 ImagePullBackOff
flaskapp-deployment-pod-3 0/1 ImagePullBackOff
After the webinar I decided to go back and take a look at the environment; and lo and behold, this is what I found!
$ kubectl get podsAnd when I did a quick search of Docker Hub Status later, this is what I discovered:
NAME READY STATUS
flaskapp-deployment-pod-1 1/1 Running
flaskapp-deployment-pod-2 1/1 Running
flaskapp-deployment-pod-3 1/1 Running
![Docker Hub issues](https://a.storyblok.com/f/153547/1091x554/61385ecae1/screen-shot-2019-10-16-at-2-17-52-pm.png)
As if by magic Docker Hub has decided to stop working within the exact time period of the Live Webinar. I learned a few things from this event:
- Don’t rely on a public repository / link for your demos
- Failures occur where you least expect them to
- Always prepare a backup
I hope you enjoyed the live session regardless, and if you didn’t attend, I'm sorry you missed out on all the fun. Here’s hoping for a more successful demo next time!