Microsoft today announced the launching of a brand-new open-source service mesh based on the Envoy proxy. The Open Service Mesh is meant to be a reference implementation of the Service Mesh Interface( SMI) spec, a standard interface for service meshes on Kubernetes that has the backing of most of the players in this ecosystem.
” SMI is really echo with folks and so we really thought that there was room in the ecosystem for a citation implementation of SMI where the mesh engineering was first and foremost implementing those SMI APIs and offsetting it the best possible SMI experience for customers ,” Microsoft director of collaborator conduct for Azure Compute( and CNCF board member) Gabe Monroy told me.
He too added that, because SMI provides the lowest common denominator API design, Open Service Mesh causes consumers the ability to ” bail out” to raw Envoy if there is a requirement to some more advanced pieces. This” no cliffs” motif, Monroy memorandum, is core to the philosophy behind Open Service Mesh.
As for its facet provide, SMI handles all of the standard service mesh boasts you’d expect, including securing the contacts between works squandering mTLS, administering access assure plans, busines surveillance and more.
There are plenty of other service mesh technologies in the market today, though. So why would Microsoft propel this?
” What our customers have been telling us is that solutions that are out there today, Istio being a good example, is very complex ,” he said.” It’s not just me saying this. We discover the data provided in the AKS support queue of customers who are trying to use this nonsense — and they’re struggling right here. This is just hard technology to use, hard-handed engineering to build at scale. And so the solutions that were out there all had something that wasn’t quite right and we really felt like something lighter weight and something with more of an SMI focus was what was going to stumble the sugared spot for the customers that are dabbling in this technology today .”
Monroy likewise noticed … … that Open Service Mesh can sit alongside other solutions like Linkerd, for example.
A lot of scholars expected Google to also bequeath its Istio service mesh to the CNCF. That move didn’t materialize.” It’s funny. A much of people are very focused on the governance aspect of this ,” he said.” I mull when people over-focus on that, you lose sight of how are patrons doing with this technology. And the truth is that customers are not having a great time with Istio in the wildernes today. I believe even tribes who are penetrating in that community will acknowledge that and that’s really the reason why we’re not interested in contributing to that ecosystem at the moment .”
Read more: feedproxy.google.com