Upgrade to Pro — share decks privately, control downloads, hide ads and more …

k8s/istio meetup 10/17

Matt Klein
October 17, 2017

k8s/istio meetup 10/17

Observability and control in the age of the service mesh: present and future

Matt Klein

October 17, 2017
Tweet

More Decks by Matt Klein

Other Decks in Technology

Transcript

  1. Observability and control in the age of the service mesh:

    present and future Matt Klein / @mattklein123, Software Engineer @Lyft
  2. What is Envoy and the service mesh? The network should

    be transparent to applications. When network and application problems do occur it should be easy to determine the source of the problem.
  3. Envoy refresher • Out of process architecture • Modern C++11

    code base • L3/L4 filter architecture • HTTP L7 filter architecture • HTTP/2 first • Service discovery and active/passive health checking • Advanced load balancing • Best in class observability (stats, logging, and tracing) • Edge proxy
  4. Observability • Observability is by far the most important thing

    that Envoy provides. • Having all SoA traffic transit through Envoy gives us a single place where we can: ◦ Produce consistent statistics for every hop ◦ Create and propagate a stable request ID / tracing context ◦ Consistent logging ◦ Distributed tracing
  5. Lyft today Legacy monolith (+Envoy) MongoDB Internet Clients “Front” Envoy

    (via TCP ELB) DynamoDB Python services (+Envoy) Obs, obs, obs, obs, obs, obs... Go services (+Envoy) Stats / tracing (direct from Envoy) Discovery
  6. State of incident handling @lyft: something breaks The page goes

    out (hopefully). What is the best case scenario of what follows?
  7. Future of microservice observability: problems • Dev/Ops have too many

    data sources that are not linked. • Cognitive load of different data sources make issue investigation with traditional stats, logging, and tracing is VERY high • Service mesh yields an observability base that allows us to do incredible things by default. How can we reimagine observability and operations in the age of the service mesh?
  8. Service portal sketch: service detail Optimal visualization of high level

    state Actions relevant to mitigation Machine learning to identify problems RBAC and versioning
  9. How do we get there? • A universal data plane

    like Envoy provides unified APIs for control as well as consistent observability output. • Allows us to build more feature-rich full service mesh solutions such as Istio. • When we assume the existence of the service mesh, we can focus on an incredible UI/UX instead of constantly trying to keep every application up to date. • Assume that service mesh is the future… All data is available. • We need to start building the UI/UX/ML of the future for distributed system command control. Need to start now!
  10. Q&A • Thanks for coming! Questions welcome on Twitter: @mattklein123

    • We are super excited about building a community around Envoy. Talk to us if you need help getting started. • Lyft is hiring!