We’re trying to use the HTTP Proxy feature mentioned here: https://k6.io/blog/k6-load-testing-debugging-using-a-web-proxy/
But it appears the proxy is used only when running it locally and not from the cloud:
HTTP_PROXY=<> HTTPS_PROXY=<> k6 run test.js - proxy working
HTTP_PROXY=<> HTTPS_PROXY=<> k6 cloud test.js - proxy ignored
We’ve also tried to set the env from the Grafana console → Performace → Setting → Environment Variables but still with no effect.
The question is whether using a custom HTTP proxy is supported for runs in the cloud or if it always uses Cloud IPs logic: Cloud IPs?
If not is there a way to use a custom HTTP proxy when running performance tests via k6 cloud test.js command? We need this because our website is hosted on a 3rd party service which might block IPs if there are too many requests. With the default Cloud IPs logic there are very few unique IPs used.
1 post - 1 participant