A variation of the theme is to also package and run your tests within Kubernetes—either in the same namespace, or in a separate namespace from your system under test. This is slower than running the tests locally, as it requires you to package your tests into a container, just as you do with your code. The trade-off is having a very consistent means of running those tests and interacting with the system-under-test.
If you work in a very diverse development environment where everyone has a slightly different setup, then this pattern can consolidate the testing so that everyone has the same experience. Additionally, where local tests need to access the remote Kubernetes through ...
