K8s display node of runner execution
Description
As described by customer:
It would be great if the k8s runner would log what physical “node” the job is executing on?
I noticed a job with IO errors only happened when it landed on particular node by looking at the cluster while it was running.
If users come to me saying their build failed then I’m not going to have any information to correlate that the node had issues across various jobs…
Asked the customer if displaying the IP address would be sufficient, however they responded that it won't work because:
We’re using the kubernetes executor here which is spinning up work pods that can land on other hosts…
Proposal
When a job is executed note which node was used so that node specific errors can be debugged.