I am having some trouble with the HTTP Step.
I was expecting that, since the harness delegate is installed in my cluster, that the HTTP Step I would be execute from inside the cluster and have access to the service-name.namespace-name kubernetes DNS, however the HTTP Step times out.
When I manually
kubectl exec -ti helm-delegate-c4c8cf44f-954mt -n harness-delegate-ng -- /bin/bash curl http://<service-name>.<namespace-name>:<service-port>
I do get the expected result, so something unexpected is happening with the the HTTP Step not resolving the DNS in the same way that a direct command from the delegate does