transportation providers across Europe and North America #IstioCon Our developer flow Develop -> PR -> master -> deploy QA -> deploy Production #IstioCon Our clusters #IstioCon The problem Running at Omio is both not efficient and cost-effective #IstioCon How tests are run ● On QA (dev -> PR -> master -> deploy QA …. ) ● On standalone VMs running all services needed for the test #IstioCon #IstioCon Define efficient and cost-effective #IstioCon 1. Minimize time to bug detection Dev -> PR -> master -> QA -> prod 3 steps away to find a problem #IstioCon 2. Allow simultaneous tests Only

night, weekdays, weekends, and holidays. Please do not ever hesitate to ask a question or send a PR.” https://github.com/istio/istio/wiki/Reviewing-Pull-Requests #IstioCon Learn Istio is a complex for documentation ○ Look into writing tests and how they work ○ We are here to help you with your PR! #IstioCon Thank you! @albertsun0 https://albert.doshy.org

#IstioCon Istio Community Number of contributors last 12 months: 350+ contributing companies 500+ PR authors 1900+ contributors Istio Community #IstioCon Service Mesh Surveys Using service mesh in

WebAssembly ecosystem is still young; 7 Wasm in Envoy Proxy ● Wasm动态加载 ● 一致性校验: ○ https://github.com/pr oxy-wasm/spec ● 内置的Wasm runtime ○ ~20MB for WAVM ○ ~10MB for V8 ● 事件驱动模型 ● 兼容native filter调用 方式

of each issue identified in the audit. Ideally, there should be a public mapping of each issue to a PR/commit with the given fix. This lack of both internal and external documentation makes it difficult