That begs the question. Why are we focused on Kubernetes, even though we want a tool that works both inside and outside Kubernetes? If I show you how to do chaos engineering on AWS, then you might say that you need examples in Azure. Or, you might prefer Google or an on-prem cluster based on VMware. It would be close to impossible for me to provide examples in all those (and other) platforms. That would require multiple courses. So, I did not want to focus on a particular hosting platform (e.g., only AWS, or only Azure) since that would not be inclusive. I wanted to make the scope as wide as possible. Therefore, the course is focused on Kubernetes, which happens to work (almost) anywhere. Everything you learn should work, more or less, in any Kubernetes distribution with any hosting provider.