Open Service Mesh (OSM) was introduced in August 2020 and joined the CNCF shortly after. Since then, OSM has been working closely with the community to provide a simplified operational service mesh experience that makes use of an interoperable set of service mesh APIs via Service Mesh Interface (SMI). An incredible amount of excitement, advancements, and shared ideas have emerged in the service mesh community, aligning with OSM’s guiding principles. Read More…

The Open Service Mesh maintainers are excited for the upcoming KubeCon + CloudNativeCon NA ‘22 in Detroit, MI! From pre-day talks to the project booth, they’ll be ready to chat with the community about the latest with OSM, answer questions, and learn how the community is using the project!

OSM’s contributors have been hard at work over the past several months preparing for the v1.0.0 release. Today, the OSM team proudly announces the release of version 1.0.0. Thanks to the community for helping drive the features they want to see in a service mesh and heightening the expectation for OSM to provide enterprise features and functionality. Reaching a project’s v1.0.0 milestone is a major accomplishment that is also met with a lot of reflection. Read More…

Today, we are excited to announce the first release candidate of Open Service Mesh (OSM) v1.0. It has been an exciting year since the initial open sourcing of the OSM project. OSM is a cloud native service mesh that allows you to uniformly manage, secure and observe application traffic in dynamic microservice environments. It runs on Kubernetes today and we’re planning to support OSM in multi-cluster and hybrid environments as well soon. With the v1.0 release coming in the next few weeks, we’ll deliver a stable set of robust service mesh features. You can use OSM to…

While Open Service Mesh (OSM) provides microservices environments with tools for security, traffic management, and observability, the project continues to evolve to support changing needs. As users deploy increasingly complex applications to Kubernetes, it’s become evident that running a service mesh across multiple clusters is desirable for application scalability and robustness.