David Harrington
11/12/2020, 5:07 PMDocker
storage for each job.
We construct the images ourselves and may have many flows. We want to avoid constructing a unique image for each specific Flow, and we also want to avoid creating an image that contains every flow. Instead, we want to provide a base image that the Kubernetes Agent can run, and subsequently the launched Job can ask for the necessary Flow at runtime.
Ultimately, we want to avoid serializing the Flow within the built image and still use the Kubernetes Agent.
A thought we had was to build an image whose entrypoint would query for the Flow, place the serialized Flow in the appropriate file location and start Prefect.
Looking for any thoughts on how to best use k8s agent with these constraints! ThanksDylan
11/12/2020, 6:49 PMDavid Harrington
11/12/2020, 6:51 PM