Hi guys When I build and apply a deployment I m getting erro

Question

Hi guys When I build and apply a deployment I m getting error below Storage block is not set thus local storage is used Infra block specifies k8s cluster and an agent works in there so basically I want to run a flow from my local storage in k8s cluster specified by infra block Any idea

redsquare · Answer

local storage is not supported for Kubernetes Jobs

Tolga Karahan · Answer

< redsquare> thanks

Tolga Karahan · Answer

Is docker storage supported for k8s jobs to pull image from a registry and run as a job

redsquare · Answer

Interesting perhaps you could fool it by setting ignore storage and setting the path to the location in the docker image <https github com PrefectHQ prefect blob main src prefect deployments py LL156C9 L156C27>

Tolga Karahan · Answer

< redsquare> so Docker storage is not supported anymore by default

redsquare · Answer

it is but not sure if you use your own docker image within a k8s job gt pod does it expect the storage to come remotely

Tolga Karahan · Answer

yeah it was how we use Prefect 1

redsquare · Answer

looks like it will be find if you set ignore storage will just use the path for the flow

Tolga Karahan · Answer

okay thanks < redsquare> pray

redsquare · Answer

wonder if you could set that attach a volume by a patch in a customization for the k8s job it would work

Tolga Karahan · Answer

I just wonder if flow code doesn t come from remote but embedded in builtin image May I use this image as the image for infra block to execute flows Thanks in advance pray

redsquare · Answer

I have not tried but see no reason for a limitation here to allow you to run a custom docker image in a k8s job and reading the flow from the image

redsquare · Answer

If you set the ignore storage to true

redsquare · Answer

you should be able to store the flows on a volume in k8s and have the pod mount the volume+exxecute the flow

Tolga Karahan · Answer

I see thank you we ll give it a try our main issue is we have quite heavy initialization so we want to use our custom image

redsquare · Answer

feels a pain to build and publish a new image everytime a flow changes

redsquare · Answer

or you add a new one

Tolga Karahan · Answer

yeah

Tolga Karahan · Answer

so it looks like using custom image as execution environment but getting flows from some storage is better

redsquare · Answer

100

Tolga Karahan · Answer

I ll try using custom image as infra block image and also a storage maybe s3 or remote git repo

redsquare · Answer

we use k8s with s3 storage works great

Tolga Karahan · Answer

your pods are also using a custom image

Tolga Karahan · Answer

or prefects own image

redsquare · Answer

currently prefects own until we are sure about common requirements across all flows then we will create a custom image but only when that is clear

redsquare · Answer

time for the flow to run is not uber critical for us currently so we have lots of pip installs

redsquare · Answer

lots = 5 15

Tolga Karahan · Answer

I see sounds good

Tolga Karahan · Answer

ML dependencies are a bit problem libraries are heavy

redsquare · Answer

yeah we are light on ML but use MindsDB on top of Clickhouse currently

Tolga Karahan · Answer

oh interesting

Tolga Karahan · Answer

I know it but didn t find any occasion to use slightly smiling face

redsquare · Answer

click or minds

Tolga Karahan · Answer

MindsDB have no idea on click smile

redsquare · Answer

They are both great clickhouse especially

Tolga Karahan · Answer

yeah mindsdb look very interesting I ll take a look to other