https://prefect.io logo
Join Slack
Powered by
Hi! I want to move my pool worker to Kubernetes, b...
# ask-community
l
Hi! I want to move my pool worker to Kubernetes, but it seems the free tier doesn’t allow adding a worker pool. I started using Prefect two years ago and it was free back then. If I delete my current worker pool, will I be unable to create a new one?
a
Hey! On free tier if you delete it you won’t be able to create a new one.
l
That's sad... I guess I have to leave Prefect soo 😬
e
What are the other options, other than prefect?
l
In my case I just wanna run python script every day and knowing which one failed or not. I guess there is some alternative. Im gonna try to self host prefect for now
n
hi @Loup - if you'd prefer to host open source prefect, here are the docs on doing so https://docs.prefect.io/v3/how-to-guides/self-hosted/server-cli let us know if you have any questions!
🦾 1
l
Ive added to my k3s cluster Prefect (using helm). Ive protected it with basic auth and a public domain to access it. Now I have to learn how to make a deployment to my custom prefect instance 😅
🙌 1
Well I have my prefect server, but my worker got an issue. In my helm setup, I have :
Copy code
repoURL: <https://prefecthq.github.io/prefect-helm>
      chart: prefect-worker
      targetRevision: 2025.11.21180339
      helm:
        valuesObject:
          worker:
            apiConfig: selfHostedServer
            config:
              workPool: kube
              jobNamespace: prefect
I specify the 
jobNamespace
because rn my deployment are crashing because of that. But the namespace still in default. Idk what I miss... Also the helm chart said :
Copy code
# -- the namespace where the jobs would spawn. If unset, spawns in the same namespace as the worker controller. Requires role.namespace to be set with the same value.
    jobNamespace: null
So its should be automatically 
prefect
after so many time is still 
default
idk how we are supposed to change it
3 Views
Open in Slack
PreviousNext
Powered by