Garden crashes due to getaddrinfo ENOTFOUND

[shumailxyz]

Crash report

Garden crashes due to a temporary network error.

Error message

✖ deploy.frontend      → Failed processing Deploy type=container name=frontend (from module frontend) (took 3.72 sec). This is what happened:

────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────
Encountered an unexpected Garden error. This is likely a bug 🍂

Please attach the following information to the bug report after making sure that the error message does not contain sensitive information:

Failed processing Deploy type=container name=frontend (from module frontend) (took 3.72 sec). This is what happened:
Error: getaddrinfo ENOTFOUND xxxxxxxx.eu-central-1.eks.amazonaws.com
    at GetAddrInfoReqWrap.onlookup [as oncomplete] (node:dns:84:26)
    at GetAddrInfoReqWrap.callbackTrampoline (node:internal/async_hooks:130:17)
────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────

toKubernetesError encountered an unknown error unexpectedly during Kubernetes API: readNamespacedSecret: toKubernetesError encountered an unknown error unexpectedly during readNamespacedSecret: getaddrinfo ENOTFOUND xxxxxxxx.eu-central-1.eks.amazonaws.com

What did you do?

ran deploy

Your environment

• OS:
• How I'm running Kubernetes:
• Garden version:

Frequency

Workaround

Run the command again.

[shumailxyz]

One suggestion would be to catch errors like getaddrinfo ENOTFOUND and add retries. Often, retrying is sufficient to address transient network issues.

[shumailxyz]

Closing in favor of #5217