Kubernetes Service Mesh with Istio [Video]

Kubernetes Service Mesh with Istio

Kubernetes Service Mesh with Istio [Video]

English | MP4 | AVC 1920×1080 | AAC 48KHz 2ch | 2h 18m | 352 MB
eLearning | Skill level: All Levels

Kubernetes Service Mesh with Istio [Video]: Hands-on traffic management, resiliency, diagnosability and security for microservice architectures with Istio and Kubernetes

Building microservice architectures is complex. Handling its complexities (such as circuit breaking, rate limiting, observability, or security) is usually left to development teams to implement.

Using well known open source frameworks is an option, but this will quickly lead to excessive library bloat and suddenly your services are not quite so micro anymore.

This course provides practical hands-on experience in using the Istio service mesh. Instead of implementing cross-cutting concerns within each service, you will see how a service mesh allows you to transparently inject and decorate the desired concerns into individual communication channels.

  • Explore the Istio architecture and its components
  • Install the Istio service mesh in Kubernetes using Helm (and manually)
  • Control ingress and egress traffic in the service mesh
  • Apply path, header, and weight-based routing strategies
  • Perform Blue/Green and Canary deployments with Istio
  • Implement service resiliency using timeouts, circuit breakers, bulkheads, and retries
  • Perform chaos testing by injecting faults and errors
  • Secure the Istio service mesh with mutual TLS and authentication/authorization policies
  • Explore and leverage Istio’s diagnosability features

We discuss the conceptual Istio architecture with its main building blocks and how it works. Then demonstrate how to install Istio and use its traffic management, resilience, diagnosability, and security features.

By the end of this course, you will be ready to deploy Istio into production and run your next cloud-native microservice architecture.

DOWNLOAD

Leave a Reply

Your email address will not be published.