application UI – Create E2E tests, component tests and service tests from the same data • Key product benefits (#releases, #rollbacks, MTTR, #bugs-in-production, Reduced eng effort for testing, velocity) – with Istio – Fewer failures higher up the test pyramid as a result of improved API tests • Istio benefits – Venky / Prasad – point here • Demo • Questions 2 Structure | CONFIDENTIAL 3 API-driven

#IstioCon Local Istiod, remote proxy Cluster go run ./pilot/cmd/pilot-discovery + All of the benefits of running Istiod locally + Can easily test real traffic, complex microservices, etc - Requires

services from networking and configuration ● Avoid other sources of failures (Consul etc) ● Possible benefits on Observability #IstioCon Requirements and Improvements ● Immutable deployments ● Minimal blast

CNI plugins setup ip for pod Istio CNI install isidecar network routing rule to workload iptable Benefits of Istio CNI No need for CAP_NET_ADMIN and CAP_NET_RAW permission No need for istio-init container

clusters for deploying, running, and managing serverless, cloud- native applications. It provides benefits: Focus on code Scale to zero Quick entry to serverless computing … … traffic management

severity security issues such as CVE-2022-23635 along with dozens of reliability issues. As such, Istio benefits largely from having a substantial fuzz test suite that runs continuously on OSS-Fuzz. Ada Logics