@Marvin I want to self-host Prefect on Kubernetes (AWS EKS). I don’t have to have a Prefect Cloud account for running flows on Kubernetes, right? I didn’t understand how to create a work pool or configure the worker when I use OSS Prefect. The docs has an example with Prefect Cloud.

@Marvin I'm trying to implement UV in my flows. How do I add a custom entrypoint to a prefect.yaml file? It should be something like "uv run main.py"

Hello! Can anyone recommend how to provision a Prefect Block which supports connecting to AWS Redshift? using standard postgres

POSTGRESQL_PSYCOPG2

results in a driver which throws the following error on connection:

sqlalchemy.exc.ProgrammingError: (psycopg2.errors.UndefinedObject) unrecognized configuration parameter "standard_conforming_strings"

This is, apparantly, a known issue: https://github.com/sqlalchemy/sqlalchemy/issues/9442 More worryingly, I cannot see any support in Prefect connectors for Redshift. Can anyone advise?

@Marvin How do I set up an s3 storage block for a self hosted prefect server using MinIO?

what's the recommended concurrency limit per work queue and per work pool when using the default task runner?

Hi all. I am interested in using Prefect to run workflows on an HPC machine with the Slurm job scheduler. However, there isn't much documentation for how to use

prefect-dask

to achieve this. Does anyone have some minimal working examples for how to dispatch individual tasks in a flow as Slurm jobs?

I’m running a prefect flow that moves a large amount of files from s3 to google cloud storage. When there are a relatively small amount of files to transfer, it’s quick. But as the files to transfer grow and especially if file size is large, the prefect process takes up increasingly large amounts of memory. I am using the

S3Download

and

GCSUpload

tasks. My suspicion is that the flow is not releasing the memory of the files being transferred. Is there any way to ensure the file contents are being released from memory?

@Marvin in prefect 3, how can I set up to run the UI from docker ?

Hey guys, I would like to instrument my self hosted Prefect deployment with

OpenTelemetry

(Its the last part of our micro-service architecture thats missing it) I was looking online and only managed to find a single old thread and one attempt that doesn't look working/maintained. Anyone tried this? Know if its doable even? • It would require passing the Open Telemetry trace id from a parent flow to each of its subflows/tasks. Prefect run context which might be an option for this does not appear to allow additional fields. • The tasks/flows themselves would also need to be instrumented of course Would appreciate any help 🙏 Thanks all

I'm getting

Unable to start worker. Please ensure you have the necessary dependencies installed to run your desired worker type.

when I tried to start the Docker worker. Not sure if this is just misconfiguration of the pool or something missing on my machine?