Istio to The Rescue: How to Tame Your Microservices Architecture
Nowadays, everybody is running microservices. And why not? They have a lot of advantages, but to be honest, there are new drawbacks to stumble upon as well.
In this workshop, we will go through some of them and explain how they can be addressed thanks to a service mesh. First, there will be a brief explanation of what Istio architecture actually is and how it works. Afterwards, it is time to apply these concepts to a real demo cluster. Bit by bit, we will go through some scenarios and try to leverage them in Istio to help us solve them.
- from 08.00 welcome desk open – coffee and snacks
- 09.00 a.m. - 10.45 a.m.: Introduction, small presentation what is Istio and how it works (theory)
- 10.45 a.m. - 11.15 a.m.: coffeebreak
- 11.15 a.m. - 12.30 p.m.: Solve problems with installation and deployment. Security (Authn and Authz)
- 12.30 p.m. - 1.30 p.m.: lunchbreak
- 1.30 p.m. - 2.45 p.m.: Traffic management (Ingress/Egress traffic and traffic routing)
- 2.45 p.m. - 3.00 p.m.: coffeebreak
- 3.00 p.m. - 4.00 p.m.: Telemetry (tracing and metrics)
- appr. 4.00 p.m. : end
- I have written down the requirements here github document. It links to some other resources that will help the attendees to configure their systems.
If you are using hardware that is company property, please make sure, if one of the following problems could occur:
- Workshop-participant has no administrator rights.
- Corporate laptop uses excessively meticulous security software.
- Set corporate-proxies, on which you are forced to communicate within the company, but which can’t connect in different environments.
* Basic knowledge of Kubernetes and/or Docker
* Experience using a terminal
* Present different approaches how to improve microservices architecture operations
* How a service mesh works