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 a ten-week series about Istio, Service Mesh, OpenShift, and Kubernetes. Part six can be found here.]

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

State of Functions-as-a-Service on Kubernetes (OpenShift Commons Briefing)

If you are interested in serverless computing / Functions-as-a-Service (FaaS), and are not following the OpenShift blog, you should checkout The State of Functions-as-a-Service on Kubernetes.  This video is part of the OpenShift Commons Briefing series, which has a lot of great content for developers who interested in cloud-native applications and microservices running on OpenShift and Kubernetes.

FaaS, or serverless as some call it, is a promising compute paradigm suitable for event-driven scenarios. In this briefing, Red Hat’s Michael Hausenblas and Brian Gracely reviewed the current open source offerings for FaaS on Kubernetes (Apache Open Whisk, kubeless, OpenFaaS, etc.) and discussed the pros and cons, on an architectural level and a user experience (UX) point of view. They also covered the topic FaaS vs. containers from a developers as well as an operators perspective.

This talk builds on material gathered by the Serverless Working Group , which is part of the Cloud Native Computing Foundation (CNCF). CNCF serves as the vendor-neutral home for many of the fastest-growing projects on GitHub, including Kubernetes, Prometheus, and Envoy.

Video, slides, and other resources:

Continue reading “State of Functions-as-a-Service on Kubernetes (OpenShift Commons Briefing)”

Share

Bringing Coolstore Microservices to the Service Mesh: Part 2–Manual Injection

Coolstore+Istio Logo

In the first part of this series we explored the Istio project and how Red Hat is committed to and actively involved in the project and working to integrate it into Kubernetes and OpenShift to bring the benefits of a service mesh to our customers and the wider communities involved. If you want to play with Istio, check out the service mesh tutorials on learn.openshift.com. If you want to install it, follow the Istio Kubernetes quickstart instructions and install it on OpenShift 3.7 or later. Also don’t miss Don Schenck’s series of blogs on Istio technology in general to learn more about it and what Red Hat is doing in this space.

In this post, we will deploy the existing Coolstore microservices demo as a service mesh and start to demonstrate the tangible value you can get out of the system without any major rewrite or rearchitecture of the existing app. We’ll also improve our project along the way to adhere to Istio (and general microservice) best practices. In the real world, your applications and developers often make bad assumptions or fail to implement best practices, so with this information you can learn something about your own projects. For Coolstore, many of these workarounds will eventually find their way into the source code of the demo.

Continue reading “Bringing Coolstore Microservices to the Service Mesh: Part 2–Manual Injection”

Share

Bringing Coolstore Microservices to the Service Mesh: Part 1 – Exploring Auto-injection

As the industry heads toward the Trough of Disillusionment with cloud-native microservices, finally understanding that distributed architectures introduce more complexity (weird, right?), services meshes can help soften the landing and shift some of that complexity out of our applications and place it where it belongs, in the application operational layer.

At Red Hat we are committed to (and actively involved in) the upstream Istio project and working to integrate it into Kubernetes and Red Hat OpenShift to bring the benefits of a service mesh to our customers and the wider communities involved. If you want to play with Istio, check out the Service Mesh Tutorials on learn.Openshift.com. If you want to install it, follow the Istio Kubernetes quickstart instructions and install it on Red Hat OpenShift 3.7 or later (or 3.9 if you want to use auto-injection).

Continue reading “Bringing Coolstore Microservices to the Service Mesh: Part 1 – Exploring Auto-injection”

Share

Red Hat OpenShift Container Platform Load Testing Tips

A large bank in the Association of Southeast Asian Nations (ASEAN) plans to develop a new mobile back-end application using microservices and container technology. They expect the platform to be able to support 10,000,000 customers with 5,000 TPS. They decided to use Red Hat OpenShift Container Platform (OCP) as the runtime platform for this application. To ensure that this platform is able to support their throughput requirements and future growth rate, they have performed internal load testing with their infrastructure and mock-up services. This article will share the lessons learned load testing Red Hat OpenShift Container Platform.

Continue reading “Red Hat OpenShift Container Platform Load Testing Tips”

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.

Once again, Istio provides the basis of a popular and well-tested technology: The Circuit Breaker Pattern.

Like a circuit breaker in an electrical circuit, the software version allows flow to a service to be shut off. The circuit opens in the case where the endpoint is not functioning correctly. The endpoint may have failed or may just be too slow, but it represents the same problem: this container is not working.

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

Share