Announcing Gloo Mesh 2.0
Today we are excited to announce version 2.0 of our enterprise-grade, Istio-based solution for multi-cluster and multi-mesh service mesh management, Gloo Mesh. This is a special milestone for Solo.io, which follows tremendous growth in our customer base, in our user community, in our team, and in the scale of innovation and support we offer organizations to adopt and extend their service mesh experience.
We announced the general availability of Gloo Mesh last year. Today, we have hundreds of enterprise customers. This includes customers running extremely large production environments, consisting of hundreds of Kubernetes clusters across multiple locations, with hundreds of million transactions per day, thousands of internal APIs, and large and diverse development teams.
At Solo our top priority is the success of our customers and we are continuously having conversations with them about their needs and requirements. Through these conversations we learn about new ways in which we can make their service mesh environments more secure and more manageable and their teams more productive. The feedback we’ve collected from hundreds of our customers is the basis for the new capabilities that make up Gloo Mesh Enterprise 2.0.
There are four main areas in which this new version offers major enhancements: new multi-tenant workspaces, an API that unifies the management of north-south and east-west traffic, a cleaner and more powerful UI for observability, and improved support for VMs.
Multi-tenant workspaces in Gloo Mesh 2.0
Suppose that you installed, registered and configured Gloo Mesh and you are now ready to delegate some of the infrastructure management to your application teams. With Gloo Mesh 2.0, you can define a workspace for each team, control the namespaces allocated to them, and set role-based access controls (RBAC) and policies. In their workspace, the application team is able to deploy their application, define policies and consume external services according to their permissions, and export their own services for use in other workspaces. Teams are provided with a graph of their services and the traffic between them, and obtain multiple metrics with a click of a button.
To learn more about multi-tenant workspaces, check out our blog, Workspaces – Multi-Tenant Application Networking APIs.
Cohesive API at the edge and in the cluster with Gloo Mesh 2.0
Our mission at Solo is to help enterprise users manage all aspects of their application networking. One of the things that has always been an annoying hurdle is the need to use different APIs for traffic management into the cluster (north-south) and within the cluster (east-west). Gloo Mesh 2.0 ends this nuisance by enabling developers to configure rules and policies for both north-south traffic and east-west traffic from a single, unified API. The new API also simplifies the process of expanding from a single cluster to dozens or hundreds of clusters.
You can find more about this new, unified API in this blog, A new API for Developers and Operators
A new clean and more powerful UI for observability in Gloo Mesh 2.0
Gloo Mesh 2.0 provides you with service topology graphs that highlight network traffic, latency, and speeds while automatically saving the new state when you move clusters or nodes. Clean icons, colors, and the size of lines provide you with better readability. Plus, you can view TCP metrics and time ranges at-a-glance and expand to full screen to see everything at once.
Improved VM Support with Gloo Mesh 2.o
Adding a VM to Istio service mesh environments is a cumbersome, multi-step process. Gloo Mesh 2.0 automates this process, reducing the required time and the chances for mistakes. It also provides support for all existing applications running in VM environments.