Don Schenck

Recent Posts

Istio Service Mesh Blog Series Recap

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.

[This is part ten of my ten-part Introduction to Istio series. My previous article was Part 9: Istio Egress: Exit Through the Gift Shop.]

Week one was an introduction to the concept of a service mesh. The concept of a Kubernetes sidecar container was explained and diagrammed, and it was the beginning of a constant theme throughout the blog posts: You don’t have to change your source code.

Continue reading “Istio Service Mesh Blog Series Recap”

Share

Istio Egress: Exit Through the Gift Shop

Using Istio with Red Hat OpenShift and Kubernetes makes life with microservices easier. Tucked away inside of Kubernetes pods, using the Istio service mesh, your code can run (mostly) in isolation. Performance, ease-of-changes, tracing, and so on are made available by simply using the Istio sidecar container model. 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 nine of my ten-part Introduction to Istio series. My previous article was Part 8: Istio Smart Canary Launch: Easing into Production.]

Continue reading “Istio Egress: Exit Through the Gift Shop”

Share

Istio Smart Canary Launch: Easing Into Production

First to fall over when the atmosphere is less than perfect

Your sensibilities are shaken by the slightest defect

You live your life like a canary in a coalmine…

When Sting and The Police sang those lyrics, I doubt they had microservices, Istio, Kubernetes, and OpenShift in mind. Yet here we are, years later, using the Canary Deployment pattern to ease code into production.

[This is part eight of my ten-week Introduction to Istio series.  My previous article was Part 7: Istio Dark Launch: Secret Services.]

Continue reading “Istio Smart Canary Launch: Easing Into Production”

Share

Istio Dark Launch: Secret Services

“Danger is my middle name” is great for spies and people of mystery, but when it comes to deploying software, boring is better. By using Istio with OpenShift and Kubernetes to ease your microservices into production, you can make deployment really, really boring. That’s good.

[This is part seven of my ten-week Introduction to Istio series about Istio, Service Mesh, Red hat OpenShift, and Kubernetes. My previous article was Part 6: Istio Chaos Engineering: I Meant to Do That.]

Boring Is Good

Not to worry, dear DevOps person; there are some exciting things in store for you. It’s just that the end result, thankfully, is boring. You want the fun of setting things in motion and then the routine of watching it just work.

Continue reading “Istio Dark Launch: Secret Services”

Share

Istio Tracing & Monitoring: Where Are You and How Fast Are You Going?

The Heisenberg Uncertainty Principle states that you cannot measure an object’s position and velocity at the same time. If it’s moving, it’s not in a location. If it’s in a location, then it has no velocity.

Thanks to some awesome open-source software, our microservices running in Red Hat OpenShift (using Kubernetes) can report both their performance and their health. Granted, they can’t violate the Uncertainty Principle, but they can help bring certainty to your cloud-native applications. Istio brings tracing and monitoring to your system with very little effort, helping you keep things humming.

[This is part five of my ten-week Introduction to Istio series.  My previous article was Part 4: Istio Circuit Breaker: When Failure Is an Option.]

Continue reading “Istio Tracing & Monitoring: Where Are You and How Fast Are You Going?”

Share

Istio Circuit Breaker: When Failure Is an Option

The phrase “Failure is not an option” is tossed about with much bravado, as though one could make something work by just their strength of will. But the fact remains, things eventually fail. Everything. How then, do you handle the inevitable failure of your microservices? Well, by combining containers, Kubernetes, Red Hat OpenShift, and Istio, we can skip over-the-top displays of swagger, let the system handle things, and get some sleep at night.

[This is part four of my ten-week Introduction to Istio series.  My previous article was Part 3: Istio Circuit Breaker: How to Handle (Pool) Ejection.]

Continue reading “Istio Circuit Breaker: When Failure Is an Option”

Share

Istio Route Rules: Telling Service Requests Where to Go

OpenShift and Kubernetes do a great job of working to make sure calls to your microservice are routed to the correct pods. After all, that’s one of the raison d’être for Kubernetes: routing and load balancing. What if, however, you want to customize the routing? What if you want to run two versions at the same time? How do Istio Route Rules handle this?

[This is part two of my ten-week Introduction to Istio series.  My previous article was Part 1: Introduction to Istio; It Makes a Mesh of Things.]

Continue reading “Istio Route Rules: Telling Service Requests Where to Go”

Share

Introduction to Istio; It Makes a Mesh Of Things

One of the key metrics or performance indicator of a microservices software architecture and environment is lead time (the amount of time it takes to get from idea to production). Many things have an impact on lead time, such as decision-making time, how quickly the code can be implemented, testing, continuous integration, etc.

[This is part one of my ten-week Introduction to Istio series.]

Continue reading “Introduction to Istio; It Makes a Mesh Of Things”

Share