diff --git a/src/data/markdown/translated-guides/en/06 Testing Guides/04 Running large tests.md b/src/data/markdown/translated-guides/en/06 Testing Guides/04 Running large tests.md
index b688e2f77f..7627e22acb 100644
--- a/src/data/markdown/translated-guides/en/06 Testing Guides/04 Running large tests.md	
+++ b/src/data/markdown/translated-guides/en/06 Testing Guides/04 Running large tests.md	
@@ -456,6 +456,8 @@ However - at this moment - the distributed execution mode of k6 is not entirely
 - Each k6 instance evaluates [Thresholds](/using-k6/thresholds) independently - excluding the results of the other k6 instances. If you want to disable the threshold execution, use [--no-thresholds](/using-k6/options#no-thresholds).
 - k6 reports the metrics individually for each instance. Depending on how you store the load test results, you'll have to aggregate some metrics to calculate them correctly.
 
+With the limitations mentioned above, we built a [kubernetes operator](https://github.com/k6io/operator) to distribute the load of a k6 test across a **k8s cluster**. Check out [this tutorial](https://k6.io/blog/running-distributed-tests-on-k8s/) for further instructions.
+
 > The k6 goal is to support a native open-source solution for distributed execution. If you want to follow the progress, subscribe to the [distributed execution issue](https://github.com/loadimpact/k6/issues/140) on GitHub.
 
 ## Large-scale tests in k6 Cloud