Bring your towel and join one of the fastest growing data communities. Welcome to our second-generation open source orchestration platform, a completely rethought approach to dataflow automation.

Prefect Community

We're routinely seeing the following unauthorized error from our prefect worker in the middle of executions:
```kubernetes.client.exceptions.ApiException: (401)
Reason: Unauthorized
HTTP response headers: HTTPHeaderDict({'Audit-Id': 'c368d011-f31a-475a-b267-ec08606dc8a9', 'Cache-Control': 'no-cache, private', 'Content-Type': 'application/json', 'Date': 'Thu, 01 Aug 2024 12:18:33 GMT', 'Content-Length': '129'})
HTTP response body: {"kind":"Status","apiVersion":"v1","metadata":{},"status":"Failure","message":"Unauthorized","reason":"Unauthorized","code":401}```
We use prefect's managed prefect-worker helm chart
```dependencies:
- name: prefect-worker
  repository: <https://prefecthq.github.io/prefect-helm>
  version: 2024.5.29222000```
Is this at all related to this version of the helm chart?

Is there any way to debug why this is happening?

We also see
```Job 'eta4-gutenberg-54ns2': Job reached backoff limit.```
for long running tasks

We are also seeing a similar issue - wondering if you guys ever found a solution for this?