youtube image
From YouTube: Breakout Session: Introduction to Service Mesh Interface & Its Benefits - W. Albertus D & Hendry W

Description

When we use templating engines for Kubernetes manifest such as Helm, it is hard to find a Helm chart provider that includes a service mesh manifest. It's because there are multiple implementations of a service mesh with distinct manifests (e.g. Istio, Traefik, Consul, etc). Therefore, when they want to make the chart support service mesh, they need to create multiple different manifests for different service mesh implementations. That reason emphasizes why an abstraction layer is needed to provide an easy-to-consume API that can be implemented by many different service mesh implementations. By using the Service Mesh Interface (SMI), users are free to adopt service mesh concepts without being bound to any particular implementation. This talk will guide you about what features Service Mesh Interface provides and how it benefits the community.