SoloCon 2021: One API for Multiple Kubernetes Clusters and Microservices. When shifting operations to a microservices architecture. Gloo Edge 2.0 represents the first “native Istio” API gateway. Gloo Edge, an Istio-integrated API gateway for multi-Kubernetes clusters at a service mesh level.
DevOps teams typically must choose among literally hundreds of tools and platforms when shifting operations to a microservices architecture. With these challenges in mind, solo.io, a leading service mesh provider, offers tools integrated with Envoy, Istio and other principal Kubernetes-management building blocks to remove many of the enormous complexities involved in the process of stitching them all together.
Solo.io recently launched Gloo Cloud, Software as a Service for service mesh. The startup now also offers what it calls a “single-pane-of-glass view” for multicluster observability with Gloo Mesh and completely integrated Istio management with the Gloo Edge 2.0 API gateway. In addition, solo.io announced full support for gRPC specifications, making its Gloo Portal the only user interface available for the open source universal RPC framework, the company says.
Solo.io and its releases are intended to help organizations move closer to a single API model to manage the entire spectrum of cloud native deployments, which was also a main theme of SoloCon 2021, solo.io’s virtual conference that took place earlier this month.
The main dilemma organizations face when deploying multiple Kubernetes clusters and microservices is “how to manage them all through a single API,” Idit Levine, founder and CEO, solo.io, told The New Stack. They also require observability across all microservices, security processes and controls and complete accessibility for their entire range of microservices — again, through a single API. Deployment, observability and security, “are three things we are focusing on,” Levine said.
Our original Kubernetes tool list was so popular that we've curated another great list of tools to help you improve your functionality with the platform.
In this article, take a look at the service mesh in the microservices world. The software industry has come a long journey and throughout this journey, Software Architecture has evolved a lot. Starting with 1-tier (Single-node), 2-tier (Client/ Server), 3-tier, and Distributed are some of the Software Architectural patterns we saw in this journey.
For teams to monitor, support, and to maintain these services is becoming a challenge so most enterprises have invested in some kind of microservices management tool.
Just as tech is revised and upgraded, so too should a tool comparison be. Service meshes act as the substrate to connect microservices, find the one for you.
Microsoft has released open service mesh (OSM), an alpha service mesh implementation compliant with the SMI specification. OSM covers standard features of a service mesh like canary releases, secure communication, and application insights, similar to other service mesh implementations like Istio, Linkerd, or Consul. Additionally, the OSM team is in the process of donating the project to the CNCF.