Skip to content

K8s Adopting Istio

kimschles edited this page Oct 10, 2019 · 1 revision

Adopting Istion on YAML at a Time

Meagan O'Keef Kubernetes Colorado, October 9, 2019

Istion by Example

Problem Statements

Microservices

  • Benefits:
    • to scale independently
    • separation of concerns/ownership
    • Faster commit-to-deploy time (velocity)
  • Challenges:
    • More complex
    • More service owners
    • More programming languages
    • More network interactions/ more hops

Kubernetes

  • Licycles containers, keeps apps alive
  • Treat a bank of servers as one (a cluster!)
  • Add more nodes as you scale

Kube doesn't...

  • How do I investigate latency?
  • Manage security policies

Service Mesh

  • An observability tool
  • A transparent layer on your comute infrastructure
  • A sidecar proxy is inject beside every service
  • Proxies can collect metrics

Istio

  • collects telemetry for every service

  • safe rollouts with traffic splitting

  • encryption in transit

  • a control plane

    • the user talks to this
    • this lives in kubernetes
  • a data plan *

Clone this wiki locally