Hi, is there any good way to update existing deployments in my CD flow without overriding the current setup? For example, I deployed a deployment without a schedule but a client that use Prefect through the UI added a schedule. Now, I just want to change the image of the deployment through the CD flow. Is there a way to update only given values instead of writing a python script that checks the deployment for existing schedule and inserting it on the .deploy function? In general, how can I make my CD flow to live peacefully with changes coming manually from the UI?😵‍💫

Hi 👋 We suddenly started seeing this error: ModuleNotFoundError(“No module named ‘prefect.orion’“)

I am trying to get the flow ID after register… is there any way ?

I'd like to use a container that defines its own `ENTRYPOINT`as the image that prefect/dask workers and schedulers run, but when I try it, Prefect seems to expect

/bin/sh

as an entrypoint. Is there any way to override that?

Hi everyone, I have a question. Can we integrate ControlFlow with Ollama or something else? I checked the documentation but can't find anything about it. I want to integrate ControlFlow with Llama 3.2 or something else.

@Marvin in a self hosted deployment when trying to create workpool the following error is presented : Select the infrastructure you want to use to execute your flow runs Infrastructure type is required

Hello Prefect Community! I know this may seem like small potatoes in the grand scheme of things but I wrote step by step documentation on how to install an instance of prefect 2 locally using .venv. really looking forward to getting a zip up sweatshirt!

I thought I would have a play with 2.0 today - tried running the code here -> https://orion-docs.prefect.io/tutorials/first-steps/ - get following error?

ValueError: the greenlet library is required to use this function. No module named 'greenlet'

Any ideas?

Hi, I’m trying to deploy Prefect 2.0 on k8s (EKS) using the default manifest provided by

prefect kubernetes manifest orion

and I’m facing some issues with the UI which seems to not be able to connect to the database (it’s empty). It’s a similar issue to this one but on k8s, not locally. The agent container communicates with the server container (API) just fine and is able to pick up flows. I’m also able to connect to the API via prefect CLI on my local machine, create work queues, deployments, trigger flows etc (which are then picked up by the k8s agent). But UI is empty and I’m not able to see/create e.g. worker queues. Any idea what I might be missing?

How do you go about setting up a volume for jobs when using the kubernetes agent? I see that

--job-template

is an option when using start, but not when using install. I'm able to set up a volume on the agent, but I realized that won't actually make the volumes available to my flows when I run them.