You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Initially, hot reloading works fine. After some time it starts reliably failing on save, with k8s auth errors:
⏳ Processing...
ℹ web → Hot reloading...
✔ web → Hot reloading... → Done (took 822 ms)
🕑 Waiting for code changes...
⏳ Processing...
ℹ web → Hot reloading...
✔ web → Hot reloading... → Done (took 948 ms)
🕑 Waiting for code changes...
⏳ Processing...
ℹ web → Hot reloading...
✖ web → Hot reloading...
Failed hot-reloading service web. Here is the output:
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
StatusCodeError from Kubernetes API - 401 - {"kind":"Status","apiVersion":"v1","metadata":{},"status":"Failure","message":"Unauthorized","reason":"Unauthorized","code":401}
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
🕑 Waiting for code changes...
⏳ Processing...
ℹ web → Hot reloading...
✖ web → Hot reloading...
Failed hot-reloading service web. Here is the output:
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
StatusCodeError from Kubernetes API - 401 - {"kind":"Status","apiVersion":"v1","metadata":{},"status":"Failure","message":"Unauthorized","reason":"Unauthorized","code":401}
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
🕑 Waiting for code changes...
⏳ Processing...
ℹ web → Hot reloading...
✖ web → Hot reloading...
Failed hot-reloading service web. Here is the output:
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
StatusCodeError from Kubernetes API - 401 - {"kind":"Status","apiVersion":"v1","metadata":{},"status":"Failure","message":"Unauthorized","reason":"Unauthorized","code":401}
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
ctrl-c'ing the process and restarting it fixes it, so I believe this is a token auth issue.
Expected behavior
No auth errors on hot reloads, and retries if there are any errors.
Additional context
We're using a kubectl exec plugin, specifically heptio-authenticator-aws, to fetch time-limited authentication tokens. This is likely what's breaking Garden (we've seen it before with other applications, since many don't implement logic to re-fetch creds after a period of time or on error). Here's what our config looks like:
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
stalebot
added
the
stale
Label that's automatically set by stalebot. Stale issues get closed after 14 days of inactivity.
label
Jan 15, 2020
Bug
Current Behavior
Initially, hot reloading works fine. After some time it starts reliably failing on save, with k8s auth errors:
ctrl-c'ing the process and restarting it fixes it, so I believe this is a token auth issue.
Expected behavior
No auth errors on hot reloads, and retries if there are any errors.
Additional context
We're using a kubectl exec plugin, specifically heptio-authenticator-aws, to fetch time-limited authentication tokens. This is likely what's breaking Garden (we've seen it before with other applications, since many don't implement logic to re-fetch creds after a period of time or on error). Here's what our config looks like:
Your environment
The text was updated successfully, but these errors were encountered: