https://prefect.io
Join Slack
Is there a way to specify a default job template for kubernetes agent in the manifests? So I am look...
# ask-community
j
Is there a way to specify a default job template for kubernetes agent in the manifests? So I am looking at https://docs.prefect.io/orchestration/agents/kubernetes.html#custom-job-template - and I tried to use the 
--job-template
on the 
prefect agent kubernetes install
command in the hope that this would work but in fact it does not - do I need to modify the containers args which are 
prefect agent kubernetes start
to use the flag?
Well that didn't work 😞 got;
Copy code
Unsupported file scheme <gs://blah/template.yml>
When the agent tried to start the flow...
I suppose I should do this in the application code then as opposed to at a default level on the agent?
k
Oh can you try 
gcs
for the scheme? Reading this code
Then it’s worth a PR to catch the 
gs
scheme too
j
Ahhh is 
gcs
an alternitive? Never knew!!
k
I dont know if that is or if it’s just Prefect parsing for it
a
based on this, seems like gs:// is more of a standard than gcs:// but it seems there are no strong conventions imposed by GCP
if you would make a PR Kevin, we would probably need to allow both to avoid breaking changes
j
I would suggest that given when you copy the URI from the gcloud ui (or ls with gsutil) you get 
gs://
that should probably be what is used? But of course as you say it may break for people so 🤷 - it works as expected with 
gcs://
so thanks!
Also this;
Copy code
data_infra git:(create-k8s-secret-sa-key-for-dbt-bq-user) ✗ gsutil ls <gcs://prefect_job_templates>
InvalidUrlError: Unrecognized scheme "gcs".
k
Yeah I’ll just add an 
or
there today
👍 1
💯 1
🙌 1
21 Views
Open in Slack
PreviousNext
Powered by

Prefect Community

Bring your towel and join one of the fastest growing data communities. Welcome to our second-generation open source orchestration platform, a completely rethought approach to dataflow automation.

Powered by