Intermittent ECONNREFUSED when running in ARC

[phil-fileread]

Describe the bug
We are experiencing intermittent ECONNREFUSED when running ARC runners in our AKS cluster.

To Reproduce
This issue is not reproducible reliably, it is happening intermittently with no identifiable pattern.

Expected behavior
Successful connection

Runner Version and Platform

Version of your runner?
helm.sh/chart: gha-rs-controller-0.10.1

OS of the machine running the runner? OSX/Windows/Linux/...
ghcr.io/actions/actions-runner:latest

What's not working?

Job Log Output

If applicable, include the relevant part of the job / step log output here. All sensitive information should already be masked out, but please double-check before pasting here.

 
Dec 26, 2024 23:10:45.216
[WORKER 2024-12-27 04:10:45Z INFO ExecutionContext] Publish step telemetry for current step {
Dec 26, 2024 23:10:45.216
[WORKER 2024-12-27 04:10:45Z INFO ExecutionContext]   "action": "Pre Job Hook",
Dec 26, 2024 23:10:45.216
[WORKER 2024-12-27 04:10:45Z INFO ExecutionContext]   "type": "runner",
Dec 26, 2024 23:10:45.216
[WORKER 2024-12-27 04:10:45Z INFO ExecutionContext]   "stage": "Post",
Dec 26, 2024 23:10:45.216
[WORKER 2024-12-27 04:10:45Z INFO ExecutionContext]   "stepId": "b635fe99-edaa-4706-a828-d341596db041",
Dec 26, 2024 23:10:45.216
[WORKER 2024-12-27 04:10:45Z INFO ExecutionContext]   "result": "failed",
 Dec 26, 2024 23:10:45.216
[WORKER 2024-12-27 04:10:45Z INFO ExecutionContext]   "errorMessages": [
 Dec 26, 2024 23:10:45.216
[WORKER 2024-12-27 04:10:45Z INFO ExecutionContext]     "Error: connect ECONNREFUSED 10.5.6.1:443",
Dec 26, 2024 23:10:45.216
[WORKER 2024-12-27 04:10:45Z INFO ExecutionContext]     "Process completed with exit code 1.",
 Dec 26, 2024 23:10:45.216
[WORKER 2024-12-27 04:10:45Z INFO ExecutionContext]     "Executing the custom container implementation failed. Please contact your self hosted runner administrator."
Dec 26, 2024 23:10:45.216
[WORKER 2024-12-27 04:10:45Z INFO ExecutionContext]   ],
Dec 26, 2024 23:10:45.216
[WORKER 2024-12-27 04:10:45Z INFO ExecutionContext]   "executionTimeInSeconds": 1,
Dec 26, 2024 23:10:45.216
[WORKER 2024-12-27 04:10:45Z INFO ExecutionContext]   "startTime": "2024-12-27T04:10:44.9555189Z",
Dec 26, 2024 23:10:45.216
[WORKER 2024-12-27 04:10:45Z INFO ExecutionContext]   "finishTime": "2024-12-27T04:10:45.2158246Z",
Dec 26, 2024 23:10:45.216
[WORKER 2024-12-27 04:10:45Z INFO ExecutionContext]   "containerHookData": "{\"hookScriptPath\":\"/home/runner/k8s/index.js\"}"
Dec 26, 2024 23:10:45.216
[WORKER 2024-12-27 04:10:45Z INFO ExecutionContext] }.

Runner and Worker's Diagnostic Logs

If applicable, add relevant diagnostic log information. Logs are located in the runner's _diag folder. The runner logs are prefixed with Runner_ and the worker logs are prefixed with Worker_. Each job run correlates to a worker log. All sensitive information should already be masked out, but please double-check before pasting here.