Helm repo add tool ends systematically with timeout

[qasmi]

I am observing a consistent pattern where invoking helm repo add is followed by repeated, seemingly unnecessary re-runs of the same command, which eventually culminates in a tracing system timeout error.

time=2025-10-05T16:35:13.325Z level=INFO msg="executing command" trace_id=f226cfabf0e8a9ae464eca3abb2ffa02 span_id=0009c3c165c732fb command=helm args="[repo add jetstack https://charts.jetstack.io]"
time=2025-10-05T16:35:13.401Z level=INFO msg="command execution successful" trace_id=f226cfabf0e8a9ae464eca3abb2ffa02 span_id=0009c3c165c732fb command=helm args="[repo add jetstack https://charts.jetstack.io]" duration=0.076222034
time=2025-10-05T16:35:16.823Z level=INFO msg="executing command" trace_id=c2a7599e5fb86d407b50592feb3d2435 span_id=55460d9b12b8be65 command=helm args="[repo add jetstack https://charts.jetstack.io]"
time=2025-10-05T16:35:16.899Z level=INFO msg="command execution successful" trace_id=c2a7599e5fb86d407b50592feb3d2435 span_id=55460d9b12b8be65 command=helm args="[repo add jetstack https://charts.jetstack.io]" duration=0.076157755
time=2025-10-05T16:35:27.638Z level=INFO msg="traces export: processor export timeout: rpc error: code = Unavailable desc = name resolver error: produced zero addresses"