@all I am facing this issue on Kubernetes helm deployment, Does anyone has a solution to it? Worker 'KubernetesWorker d7daa483-b7b2-412f-b8cd-c46ab538422d' started! Traceback (most recent call last): File "/usr/local/lib/python3.11/site-packages/prefect/cli/_utilities.py", line 41, in wrapper return fn(*args, **kwargs) ^^^^^^^^^^^^^^^^^^^ File "/usr/local/lib/python3.11/site-packages/prefect/utilities/asyncutils.py", line 260, in coroutine_wrapper return call() ^^^^^^ File "/usr/local/lib/python3.11/site-packages/prefect/_internal/concurrency/calls.py", line 245, in call return self.result() ^^^^^^^^^^^^^ File "/usr/local/lib/python3.11/site-packages/prefect/_internal/concurrency/calls.py", line 173, in result return self.future.result(timeout=timeout) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/local/lib/python3.11/concurrent/futures/_base.py", line 449, in result return self.__get_result() ^^^^^^^^^^^^^^^^^^^ File "/usr/local/lib/python3.11/concurrent/futures/_base.py", line 401, in __get_result raise self._exception File "/usr/local/lib/python3.11/site-packages/prefect/_internal/concurrency/calls.py", line 218, in _run_async result = await coro ^^^^^^^^^^ File "/usr/local/lib/python3.11/site-packages/prefect/cli/worker.py", line 113, in start await worker.sync_with_backend() File "/usr/local/lib/python3.11/site-packages/prefect/workers/base.py", line 624, in sync_with_backend await self._update_local_work_pool_info() File "/usr/local/lib/python3.11/site-packages/prefect/workers/base.py", line 579, in _update_local_work_pool_info work_pool = await self._client.read_work_pool( ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/local/lib/python3.11/site-packages/prefect/client/orchestration.py", line 2125, in read_work_pool response = await self._client.get(f"/work_pools/{work_pool_name}") ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/local/lib/python3.11/site-packages/httpx/_client.py", line 1754, in get return await self.request( ^^^^^^^^^^^^^^^^^^^ File "/usr/local/lib/python3.11/site-packages/httpx/_client.py", line 1530, in request return await self.send(request, auth=auth, follow_redirects=follow_redirects) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/local/lib/python3.11/site-packages/prefect/client/base.py", line 280, in send response.raise_for_status() File "/usr/local/lib/python3.11/site-packages/prefect/client/base.py", line 137, in raise_for_status raise PrefectHTTPStatusError.from_httpx_error(exc) from exc.cause prefect.exceptions.PrefectHTTPStatusError: Client error '405 Method Not Allowed' for url 'http://prefect-server:4200/api/work_pools/' Response: {'detail': 'Method Not Allowed'} For more information check: https://httpstatuses.com/405

Hey @imran! Did you provide a work pool name to the helm chart when deploying your worker?

nope

If you provide a work pool name to your helm chart, the worker will create the work pool if it doesn’t exist. You can also give it a pre-existing work pool, but it needs a work pool name to function correctly.

thanks, will check and test it

How did you create the work pool? Via the UI or did your worker create it?