I'm trying to run a benchmark with a -resolvers flag within a kubernetes cluster
Kubernetes internal DNS is resolving example-host to 172.25.13.96
Here is my curl call
curl -X GET example-host:8080/liveness -w %{http_code} <- Returns 200
curl -X GET example-host:8080/liveness --connect-to example-host:8080:172.25.13.96 -w %{http_code} <- Returns 200 if I force the IP resolution
Here are my vegeta benchmarks, run from within the cluster
This benchmark is returning 200 status code, as the host is resolved with the internal DNS
Am I using the flag incorrectly? Is there a way to get more output from vegeta, to see why the calls are failing?
Also, I know that the flag is useless in that case, but I have another benchmark where I will need it
Here is just a minimal example reproducing the behavior
Question
Hello
I'm trying to run a benchmark with a -resolvers flag within a kubernetes cluster Kubernetes internal DNS is resolving
example-host
to172.25.13.96
Here is my curl call
Here are my vegeta benchmarks, run from within the cluster
This benchmark is returning 200 status code, as the host is resolved with the internal DNS
This benchmark is failing, returning 0 status code
Am I using the flag incorrectly? Is there a way to get more output from vegeta, to see why the calls are failing?
Also, I know that the flag is useless in that case, but I have another benchmark where I will need it Here is just a minimal example reproducing the behavior