Failure to contact K8s cluster hangs the `execute` step

A sample failure during the execute step where the cluster configuration kubectl was different from the cluster created in setup step -

Mar 02, 2023 11:21:55 AM com.google.cloud.machmeter.plugins.ExecutePlugin execute
INFO: Executing kubectl cp /usr/local/google/home/sunnsing/git/machmeter/machmeter/usecases/gaming/online-matchmaking/templates/data-load.jmx -n spanner-test "$(kubectl get po -n spanner-test | grep jmeter-master | awk '{print $1}'):/data-load.jmx"
Unable to connect to the server: dial tcp 34.171.187.3:443: connect: connection timed out
error: filespec must match the canonical format: [[namespace/]pod:]file/path
Fail!

Mar 02, 2023 11:23:22 AM com.google.cloud.machmeter.plugins.ExecutePlugin lambda$execute$0
INFO: Shutting down the execute...
^CFail!

^C^C^C^C^C^C

The shell process doesn't respond to ^C and the relevant Java process has to be force killed.

Expected - Shutdown should happen by-itself or at least respond to SIGINT and then get killed.