Don Schenck

The past nine weeks of blog posts have introduced, explained, and demonstrated some of the many features of the Istio service mesh when combined it is with Red Hat OpenShift and Kubernetes. This, the final post in this series, is a recap.

Using Istio with Red Hat OpenShift and Kubernetes makes life with microservices easier. But what if you want your microservice to talk to another service that is outside of your OpenShift/Kubernetes/pods environment? Enter Istio Egress.

This is part eight of a ten-week series and covers using the Canary Deployment pattern to ease code into production. Istio makes this easy while giving you several good options for intelligent routing. And you can do it all without changing your source code.

Discover how using Istio with OpenShift and Kubernetes eases microservices production and deployment. (Part 7 of 10 in a series)

Testing software is challenging and very important. Testing for correctness is one thing, but testing for failures in network reliability is quite another task. This article will demonstrate how Istio makes this oh so easy.

Istio brings tracing and monitoring to your system with very little effort, helping you keep things humming. This article covers Istio Tracing & Monitoring: Where are you are and how fast are you going?

The phrase "Failure is not an option" is tossed about with much bravado, with Istio Circuit Breaker. But the fact remains, things eventually fail. Everything. How, then, do you handle the inevitable failure of your microservices? This article will show you how.

This is week three of a ten-week series about Istio, kubernetes and OpenShift. The series started with an introduction to Istio, and this week covers Istio Circuit Breaker: How To Handle (Pool) Ejection.