While a step runner is a simple component that doesn't require any special configuration or treatment, being able to audit its operations and, when required, troubleshoot its activity can help resolve challenging situations. The below commands suggest how to get an insight into an activity performed by a step runner.
Step execution events
All steps are executed in the Kubernetes namespace called "torq" (Kubernetes is assumed as a default step runner adapter).
Using kubectl to get the list of events that took place in the namespace using kubectl get events --namespace=torq
The output should consist of the following types of events:
Pulled: Container image for a specific step was pulled from the container registry
Created: Container, based on the pulled image, was created in preparation to execute the step
Started: Step container execution started
Additional events can indicate longer processes, such as Pulling, Scheduled, and others.
Find step execution jobs
When workflows are running, steps are initiated by the step runner as jobs in the torq Kubernetes namespace. To view the currently-running jobs, use kubectl get jobs --namespace=torq
Pull step runner logs
The step runner is a Kubernetes Pod running in the "torq" namespace. In order to retrieve its logs, first one should find the Pod name by issuing kubectl get pods --namespace=torq
Then, using the Pod name retrieved, to see the detailed logs using kubectl logs --namespace=torq
Locate Runner
If you want to find a runner's IP address, copy and paste this cURL command into an empty spot in your workflow canvas and select to run in from your runner
curl 'https://api.ipify.org?format=json' {"ip":"92.178.82.94"}