Most of the tools that we use for our end-to-end testing allow the use of namespaces (not linux namespaces) to run the containers. Therefore, instead of running all our tests in the default namespace, we can create one only for the purpose of our end-to-end tests. Such a design would be also useful for cleaning up and making sure we do not leave any rubbish in the host of the end-to-end testing
Most of the tools that we use for our end-to-end testing allow the use of namespaces (not linux namespaces) to run the containers. Therefore, instead of running all our tests in the default namespace, we can create one only for the purpose of our end-to-end tests. Such a design would be also useful for cleaning up and making sure we do not leave any rubbish in the host of the end-to-end testing