-
Notifications
You must be signed in to change notification settings - Fork 735
Home
Richard Chesterwood edited this page Aug 30, 2019
·
13 revisions
We're going to have a series of scenarios, angled to where a specific feature of Istio can help. Here's the list, I'll mark off progress as I go along...
- Canary on the web front end.
- Canary on a backend microservice
- Header for a specific user (front end only)
- might do this as part of envoy session. Use AOP as way in, so could do some trivial tracing as demo
- break a lower level microservice and check that the front end isn't affect (need a "static" html for this - staff management?)
- show a heavily loaded component (eg tracker) failing (possibly with injected fault) and show (somehow) that this can cascade upwards, causing failures elsewhere. Introduce a circuit breaker
- Not sure how we could pull this off? Staging/Production minikube?
- show a call to a remote system somewhere. (need an idea on what?) Want to switch off external calls generally.
- Have the simulator run too fast for the tracker (maybe frig a delay into here). Show we can slow traffic down - what happens?
- Mmmm - interesting! Investigate, urgently, could be a solution for header propagation.
- how this is different to authorization in security.
- show we can have ONLY allowed microservices calling others. (think of example)
- show how to enable SSL within the cluster. How to demo this? Might need tracing, so this section might come last!