Open Service Mesh ingress with Gloo API Gateway (w/ Video!)
Last week, Microsoft Azure announced a new open-source project called Open Service Mesh. OSM is a new service-mesh implementation based on Envoy Proxy (yay!) that implements the Service Mesh Interface (SMI). SMI, as you’ll recall, is heavily inspired from our service-mesh abstraction vision that we predicted back in November 2018. Solo.io Service Mesh Hub is a full-fledged implementation of this vision.
With OSM, we can use SMI and Envoy on Kubernetes and get a simplified service-mesh implementation. Service mesh implementations focus on solving service-to-service communication challenges and OSM is no different. Getting traffic into the service mesh, however, is a different exercise. Often times folks gloss over it by sticking a simple ingress in that role until they realize they need more capabilities at the edge.
That’s where an API Gateway like Gloo fits in. Since Gloo is built on Envoy, its configuration is dynamic and scalable (see this article comparing other Envoy gateways and even NGINX ingress). Gloo provides capabilities like request transformation, rate limiting, and extensible AuthZ/N capabilities like (in Gloo Enterprise) Web App Firewall, Open Policy Agent, OIDC/OAuth2, and many others.
If you check out the Ingress documentation for OSM, you should see instructions for configuring Gloo to provide Ingress capabilities to the mesh. In this short video, we demo OSM and Gloo integration:
Check out Open Service Mesh and Gloo for more details, or reach out to us on Slack!
At Solo.io we work on products that enable enterprises to succeed with service mesh and Envoy-based technology to build decentralized API infrastructure. Reach out to us if you’re interested in learning more about our solutions
