KCNA · Question #182
What is the common standard for Service Meshes?
The correct answer is C. Service Mesh Interface (SMI). The Service Mesh Interface (SMI) is a standard specification that defines a common set of APIs for service meshes on Kubernetes. It enables interoperability and consistency across different service mesh implementations.
Question
What is the common standard for Service Meshes?
Options
- AService Mesh Specification (SMS)
- BService Mesh Technology (SMT)
- CService Mesh Interface (SMI)
- DService Mesh Function (SMF)
How the community answered
(34 responses)- A3% (1)
- B6% (2)
- C88% (30)
- D3% (1)
Why each option
The Service Mesh Interface (SMI) is a standard specification that defines a common set of APIs for service meshes on Kubernetes. It enables interoperability and consistency across different service mesh implementations.
Service Mesh Specification (SMS) is not a recognized or common standard name for service meshes.
Service Mesh Technology (SMT) is a generic term describing the technology, not a specific standard or interface.
The Service Mesh Interface (SMI) is a standardized specification that provides a common framework for interacting with various service mesh technologies within Kubernetes environments. SMI defines basic traffic management capabilities like traffic split, access control, and observability, allowing developers to use a consistent set of tools and APIs regardless of the underlying service mesh (e.g., Linkerd, Istio).
Service Mesh Function (SMF) is not a recognized standard or specific interface within the service mesh ecosystem.
Concept tested: Service Mesh Interface (SMI) standard
Source: https://smi-spec.io/
Topics
Community Discussion
No community discussion yet for this question.