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
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
l
Lucien Fregosi
07/22/2022, 7:42 AMHi 👋 I’m testing Prefect 2.0 kubernetes/Helm deployment
Everything seems fine expected that the agent got an issue when launching the job because the namespace and the service account are set with default value. Is it possible to override these value ? I didn’t found it in the doc
✅ 1
a
Anna Geller
07/22/2022, 9:46 AMyes, you can do that in metadata section of your K8s manifest
l
Lucien Fregosi
07/25/2022, 10:51 AMhmm that’s weird @Anna Geller the namespace is set for the agent deployment in the metadata section (i can deploy only in this namespace).
I found it, it should be added to the Deployment configuration
name="k8s-example",
flow=my_kubernetes_flow,
flow_runner=KubernetesFlowRunner(namespace="prefect", service_account_name="prefect-sa")
)✅ 1
🙌 1