This is a work in progress as I’m currently integrating the Frank Ozz Microservices application into Istio and changing it (if needed) to take advantage of Istio.
Label your default namespace to allow sidecar containers to inject themselves into the pods in your namespace.
Canary Deployment using VirtualService/DestinationRule
Istio Gateway – Allows us to configure an Edge Proxy so that you can load balance traffic coming into the proxy. They gave you the Istio Ingress Gateway container proxy to allow you to route incoming traffic thru the proxy so that you can take advantage of the VirtualService proxy.
kubectl get po -n istio-system should show
istio-ingressgateway
kubectl get svc -n istio-system should show the ingressgateway and the cluster port that we should always be able to access.
Dark Release – The ability to test (in production) releases via headers using header propogation.
Fault Injection – The ability to inject faults (for testing) into your services to see how pods respond in real world situations where faults occur.
Circuit Breakers – The ability to setup governer switches to adjust themselves (in real time) to error situations/faults to prevent cascading failures in bringing down / hurting the performance of your running pods in a cluster.
Here’s a demo (in parts) of Istio along with some courses I recommend
Part 1
Part 2
Part 3 (Includes Dark Releases)
Part 4 (Includes Canary Deployments)