You can use taints, tolerations, affinity and anti-affinity of k8s to schedule the load-generator to a different node than the one contains the service under te

You can use taints, tolerations, affinity and anti-affinity of k8s to schedule the load-generator to a different node than the one contains the service under test. The load-gen and the service does not need to be co-located in case of REST (drill) and PostgreSQL (pgbench) based load testing. In case of pure network benchmarking (with iperf & qperf) currently only the same cluster is supported.