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.

Further details

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.

Proposal

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)

Links / references

• https://cloud.google.com/blog/products/application-development/kubernetes-users-get-ready-for-the-next-chapter-in-microservices-management