https://prefect.io
Join Slack
I deployed the prefect-worker via helm to our K8 cluster, but when the pod starts I get `prefect.exc...
# prefect-kubernetes
j
I deployed the prefect-worker via helm to our K8 cluster, but when the pod starts I get 
prefect.exceptions.PrefectHTTPStatusError: Client error '405 Method Not Allowed' for url <https://api.prefect.cloud/api/accounts/{account_id}/workspaces/{workspace_id}/work_pools/>
, however, the service account we are using does have developer permissions so I am not sure based off the url I get if it’s trying to grab a workpool that already exists? (in this case it would be the default workpool since that’s the default for the helm chart)
✅ 1
Although looking at the chart it seems that the description says it uses the default pool but the default value is empty, so could that be it where it’s trying to grab the workpool but none is actually being provided?
j
hm it shouldnt be that — when a workspace is created, a default workpool is created as well. If a workpool isnt provided, the default one will be assumed
actually, let me double check that
ok i’m able to reproduce this
So yep - a work-pool is 
required
- will update the helm chart docs now
thanks for raising!
🙌 1
j
Okay thank you! I also noticed that if someone uses the default pool, it’s configured for prefect-agent not kubernetes
But that’s solved since I made a work pool and set the type to kubernetes so I don’t think that’s necessarily an issue!
j
ok great - thank you again!
I think the new behavior is not create a default work pool of type agent
j
Okay gotcha that makes sense! Thank you again!
j
anytime 🏄
Open in Slack
PreviousNext
Powered by

Prefect Community

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.

Powered by