Channels
pacc-may-31-2023
prefect-ai
pacc-clearcover-june-12-2023
marvin-in-the-wild
data-ecosystem
geo-israel
pacc-june-14-2023
geo-japan
pacc-london-2023
prefect-cloud
ppcc-may-16-2023
prefect-azure
prefect-docker
prefect-recipes
gratitude
geo-nyc
geo-bay-area
geo-boston
geo-london
geo-dc
geo-chicago
geo-berlin
geo-texas
geo-seattle
geo-colorado
prefect-community
data-tricks-and-tips
prefect-aws
prefect-gcp
introductions
find-a-prefect-job
prefect-dbt
random
events
ask-marvin
show-us-what-you-got
prefect-getting-started
prefect-integrations
prefect-contributors
best-practices-coordination-plane
announcements
prefect-server
prefect-ui
prefect-kubernetes
Title
d
Davide at Evo
05/16/2022, 2:26 PMHi! I'm evaluating Prefect for our company and so far it's excellent, although (I'm using version 2) I'm stuck with k8s jobs not being able to pull images from my custom registry. Our deployment would take advantage of custom images at flow level to support custom packages deployed by a CI. You can specify an image KubernetesFlowRunner(namespace="prefect", image="my.registry:5001/something") but in the Orion branch I cannot find any code related to the imagePullSecrets config.
Thanks!!
Got it by myself. As a workaround, add a default for sa user:
kubectl patch sa default -n prefect -p '"imagePullSecrets": [{"name": "gitlab-secret" }]'a
Anna Geller
05/16/2022, 3:03 PMnice work! the latest version also has the argument
service_account_name👍 1