Ops interface to Istio
Problem to solve
Ops teams need ability to change running systems without changing source code; to decouple operations from development. Istio supports this by letting Ops change various policies like retries and circuit-breaking, and by configuring runtime configuration such as traffic redirection.
If we include Istio as part of Auto DevOps, or more broadly, Serverless Apps and Functions, and provide a UI to manage common (and uncommon) operations settings, it could be a strong component of our Configure stage.
What does success look like, and how can we measure that?
(If no way to measure success, link to an issue that will implement a way to measure this)