Service Mesh


Getting Started with AWS App Mesh and Service Mesh

Companies today are breaking down their big monolithic applications into multiple microservices and one of the challenges of having to deal with multiple microservices is that it’s difficult to isolate issues such as: With microservices, there is also no dynamic way to reroute network traffic when failures occur or new containers need to be deployed.


How to monitor istiod

Istio is a service mesh that enables teams to manage traffic in distributed workloads without modifying the workloads themselves, making it easier to implement load balancing, canarying, circuit breakers, and other design choices. Versions of Istio prior to 1.5 adopted a microservices architecture and deployed each Istio component as an independently scalable Kubernetes pod. Version 1.5 signalled a change in course, moving all of its components into a single binary, istiod.


Multi-Cluster & Multi-Cloud Service Meshes With CNCF's Kuma and Envoy

When we first created Kuma – which means “bear” in Japanese – we dreamed of creating a service mesh that could run across every cluster, every cloud and every application. These are all requirements that large organizations must implement to support their application teams across a wide variety of architectures and platforms: VMs, Kubernetes, AWS, GCP and so on.

Kong Demo: Protecting Microservices with Servicemesh

In this interactive demo, we will show how to encrypt and protect all services inside a service mesh using the Kuma Mutual TLS policy. We will then demonstrate how to control traffic permissions among each individual service using the TrafficPermission policy. In addition to security, Kuma provides traffic metrics using Prometheus and Grafana dashboards, as well as traffic tracing (APM) and traffic logging integrated into managed cloud logging and analytics services.

Deploying Citrix ADC with Service Mesh on Rancher

As a network of microservices changes and grows, the interactions between them can be difficult to manage and understand. That’s why it’s handy to have a service mesh as a separate infrastructure layer. A service mesh is an approach to solving microservices at scale. It handles routing and terminating traffic, monitoring and tracing, service delivery and routing, load balancing, circuit breaking and mutual authentication.

Implementing Canary Releases on Kubernetes with Spinnaker, Istio, and Prometheus

In a microservices world, applications consist of dozens, hundreds, or even thousands of components. Manually deploying and verifying deployment quality in production is virtually impossible. Kubernetes, which natively supports rolling updates, enables blue-green application deployments with Spinnaker. However, the gradual rollout is a feature that doesn’t come out-of-the-box but can be achieved by adding Istio and Prometheus to the equation.

Kuma 0.6.0 Released With Hybrid Universal Support for Service Mesh and CNCF Donation

We are happy to announce the much-anticipated Kuma 0.6 release! This new release ships with major improvements, especially when it comes to supporting service meshes that can span across multiple clouds, multiple Kubernetes clusters and hybrid platforms (Kubernetes + VMs) in enterprise environments. Kuma has also been donated to the CNCF as a Sandbox project: the first Envoy-based service mesh to ever be donated to the foundation. Let’s unwrap these announcements.