Which framework is recognised as the standardised interface specification for service meshes?

Which framework is recognised as the standardised interface specification for service meshes?

• A. ServiceMeshInterface (SMI)
• B. Istio
• C. Linkerd
• D. Consul

Answer: (A)

Standardising the way service meshes are controlled is achieved by a framework that defines a common set of APIs and resources a mesh should support. This creates a vendor-agnostic contract so tooling and policies can be applied across different meshes without needing to learn each mesh’s unique API. That framework is ServiceMeshInterface (SMI). SMI describes a minimal, practical interface for traffic management, policy, and telemetry that multiple meshes can implement, enabling interoperability. The other options refer to actual service mesh implementations themselves (Istio, Linkerd, Consul) rather than a universal interface. They provide their own APIs and CRDs, which means tooling written for one mesh doesn’t automatically work for others.

Standardising the way service meshes are controlled is achieved by a framework that defines a common set of APIs and resources a mesh should support. This creates a vendor-agnostic contract so tooling and policies can be applied across different meshes without needing to learn each mesh’s unique API. That framework is ServiceMeshInterface (SMI). SMI describes a minimal, practical interface for traffic management, policy, and telemetry that multiple meshes can implement, enabling interoperability.

The other options refer to actual service mesh implementations themselves (Istio, Linkerd, Consul) rather than a universal interface. They provide their own APIs and CRDs, which means tooling written for one mesh doesn’t automatically work for others.