Remove xk6-kubernetes from xk6-disruptor build

Signed-off-by: Pablo Chacin <[email protected]>

Author: pablochacin

src/data/markdown/docs/40 xk6-disruptor/01 Get started/03 Installation.md

@@ -33,23 +33,10 @@ git clone https://github.com/grafana/xk6-disruptor.git
 cd xk6-disruptor
 
 # Build the custom binary 
-xk6 build --output xk6-disruptor --with github.com/grafana/xk6-disruptor=. --with github.com/grafana/xk6-kubernetes
-```
-
-</CodeGroup>
-
-
-Notice that the `build` command includes both the xk6-disruptor and the [xk6-kubernetes extension](https://github.com/grafana/xk6-kubernetes).
-This is because many example scripts use the `xk6-kubernetes` extension to create the Kubernetes resources they need, such as Pods and Services.
-If you don't use this extension in your tests, you can build the custom `k6` binary with only the `xk6-disruptor` extension using the following command instead:
-
-
-<CodeGroup labels={["Linux/MacOS"]}>
-
-```bash
 xk6 build --output xk6-disruptor --with github.com/grafana/xk6-disruptor=.
 ```
 
 </CodeGroup>
 
+
 xk6 will create the `xk6-disruptor` binary in the current working directory.

src/data/markdown/docs/40 xk6-disruptor/04 Examples.md

@@ -4,10 +4,9 @@ excerpt: 'Examples of how to use the xk6-disruptor extension to introduce faults
 ---
 
 In these sections we present some examples of how to use the `xk6-disruptor` extension to introduce faults in `k6` tests.
-Some examples use the [k6-kubernetes](http://github.com/grafana/xk6-kubernetes) extension.
-So, to follow, ensure the custom `k6` binary you are using is built with both `xk6-disruptor` and `xk6-kubernetes` extensions. See the [Installation guide](/javascript-api/xk6-disruptor/get-started/installation/) for details.
 
-Also check that your test environment satisfies the requirements described in the [get started guide](/javascript-api/xk6-disruptor/get-started/requirements/).
+
+Check that your test environment satisfies the requirements described in the [get started guide](/javascript-api/xk6-disruptor/get-started/requirements/).
 In particular, check that:
 - You have the properly configured the credentials to access the Kubernetes cluster used for the test 
 - This cluster is configured to expose your application using an external IP.