The ServiceMeshInterface (SMI) specification provides what kind of abstraction for service meshes?

The ServiceMeshInterface (SMI) specification provides what kind of abstraction for service meshes?

• A. A deployment model for pods
• B. A data plane component for mesh networking
• C. A standardised interface for traffic policy across meshes
• D. A monitoring dashboard for service meshes

Answer: (C)

SMI provides a standardised interface for traffic policy across service meshes. It defines a vendor-agnostic set of abstractions that describe how traffic should be routed and governed between services, and are implemented by different meshes. This lets you declare policies once and apply them across multiple meshes, enabling portability and interoperability. It decouples policy from the underlying data plane, so changing the mesh doesn’t require rewriting routing rules. It’s not about pod deployment models, its own data plane components, or a monitoring dashboard—the policy interface is the common layer that sits above those mesh-specific implementations.

SMI provides a standardised interface for traffic policy across service meshes. It defines a vendor-agnostic set of abstractions that describe how traffic should be routed and governed between services, and are implemented by different meshes. This lets you declare policies once and apply them across multiple meshes, enabling portability and interoperability. It decouples policy from the underlying data plane, so changing the mesh doesn’t require rewriting routing rules. It’s not about pod deployment models, its own data plane components, or a monitoring dashboard—the policy interface is the common layer that sits above those mesh-specific implementations.