Kubeflow & Istio, a Perfect Match! Investigating Istio’s Role in MLOps - Nina Polshakova & Peter Jausovec, Solo.io#

Nina Polshakova, Senior Principal Software Engineer, and Peter Jausovec, Software Architect, Solo.io

• Why: Serving ML models reliably (canary releases, authN/Z, traffic mirroring, failover) is where service mesh and MLOps actually intersect — this explains exactly what Istio is doing under Kubeflow/KServe, which most K8s practitioners using KServe never see.
• What: A breakdown of how KServe's custom resources translate into Istio resources, the minimum viable Istio configuration for secure ML operations, and how to layer canary model releases, traffic mirroring, fault injection, failover, rate limiting, external auth, and BYO Wasm plugins on the generated Kubeflow/KServe config. (from abstract only)
• How: Demonstrates the mapping from KServe CRs to Istio CRs and shows that the "hard" MLOps requirements are mesh concerns — configuration that Kubeflow abstracts away but that you must understand to operate and extend.
• Where applicable: Any Kubernetes environment running Kubeflow/KServe with Istio; general cloud-native technique, not org-specific. Vendor (Solo.io) speakers, but the content is a mechanism walkthrough of widely used OSS rather than a product demo.