Learn Istio by example and a bit of Golang!
- Chapter 00: High level plan
- Chapter 01: Application architecture
- Chapter 02: Implementing application
- Chapter 03: Installing application w/Helmfile
- Chapter 04: Running application performance tests
- Chapter 05: Installing Istio + istioctl
- Chapter 06: Istio: tracing
- Chapter 07: Istio: observability
- Chapter 08: Istio: gateway and SSL w/cert-manager
- Chapter 09: Istio: routing - basic traffic splitting
- Chapter 10: Istio: routing - advanced traffic splitting
- Chapter 11: Istio: routing - sticky sessions
- Chapter 12: Istio: routing - mirroring (dark traffic and live debugging)
- Chapter 13: Istio: fault injection
- Chapter 14: Istio: circuit breakers
- Chapter 15: Istio: JWT
- Chapter 16: Istio: mTLS
- Chapter 17: Istio: egress
- Chapter 18: Running application performance tests
- Chapter 19: Istio: multicluster setup
This is about you learning Istio. If you want of course. And story behind is.. I need an Istio crash course. A practical one, not theoretical. Usually in that kind of situations I basically try installing, configuring and working with a service. However, in case of Istio you need a whole application in order to test Istio features.
I thought - I'm gonna create a plan of learning and share it with others. Usually, when I learn something, the next thing to do is a presentation on a meetup or a conference. However, this time I feel like needing more motivation, so I decided to go public and invite other to learn with me.
So, here we are :)
I'll post updates here (simply turn on watching custom events / pull requests for this repository) or follow me on Twitter or follow hastag #golearnistio
Each "chapter" will specify a part that is to be READ by you (and ofc understand / process).
Also there will be a HOMEWORK part.
Beside notes, that are 100% enought to run this workshop yourself in your lab, I'm running a youtube stream for each chapter. I'm basically recording my work. The stream is available here: golearnistio stream
Whatever it needs. I'll probably post daily, so we move forward. But can't tell if it's one month or two when we finish.
The best way imo will be use Github Discussions. We're a community, thus we should help each other instead of funneling problems via just one person.