From 1623adbb31478651b85ca0870eb7837e27307c28 Mon Sep 17 00:00:00 2001 From: Manuel Gerding Date: Tue, 26 Nov 2024 15:07:35 +0100 Subject: [PATCH] feat: Adding docs for migrating to client locations --- README.md | 16 ++++++++++++++++ 1 file changed, 16 insertions(+) diff --git a/README.md b/README.md index 7233852..b768522 100755 --- a/README.md +++ b/README.md @@ -62,3 +62,19 @@ This extension is currently not available as a Linux package. Make sure that the extension is registered with the agent. In most cases this is done automatically. Please refer to the [documentation](https://docs.steadybit.com/install-and-configure/install-agent/extension-discovery) for more information about extension registration and how to verify. + +## Location Selection +When multiple Gatling extensions are deployed in different subsystems (e.g., multiple Kubernetes clusters), it can be tricky to ensure that the load test is performed from the right location when testing cluster-internal URLs or having different load testing hardware sizings. +To solve this, you can activate the location selection feature. +Once you do that, the Gatling extension discovers itself as a Gatling location. +When configuring the experiment, you can optionally define which extension's deployment should execute the loadtest. +Also, the execution locations are part of Steadybit's environment concept, so you can assign permissions for execution locations. + +### Migration Guideline +Before activating the location selection feature, be sure to follow these steps: +1. The installed agent version needs to be >= X.XX, and - only for on-prem customers - the platform version needs to be >=X.X +2. Activate the location selection via environment or helm variable when deploying the latest extension version (see [configuration options](#configuration). +3. Configure every environment that should be able to run Gatling load tests by including the execution location in the environment configuration. + One option is to add the statement `or target via the query language.type="com.steadybit.extension_gatling.location"` to your existing query. + You can also filter the available execution locations down, e.g., via the clustername by using `(target.type="com.steadybit.extension_gatling.location" and k8s.cluster-name="CLUSTER-NAME")` +