I'm trying to run a workflow using the VertexAgent. I enabled the Vertex API on our GCP account, but I got the following error. Do you know how to set these values?

The error looks like it came from Kubernetes, rather than from Vertex. Can you explain your setup? 1. Do you sue Prefect Cloud or Server? 2. How did you start this Vertex agent? 3. Can you share your run config from the flow that resulted in this error?

1. Prefect Cloud 2. I ran

prefect vertex agent start

on the command line 3. It's the default vertex run config

flow.run_config = VertexRun()

it looks like either your GCP project, region or service account are not configured on the machine from which you start the VertexAgent - you can either configure those with gcloud CLI or pass those explicitly on the “prefect agent vertex start” as described here

got it - I'll give it a try

tokens are deprecated, you should use --key instead

Yep, that fixed it

sorry for digging this thread again. I’m running into the same errors and just want to confirm that Vertex agent can work with prefect server edition? By adding some logging I can see that some Prefect Cloud envs are being passed when running flow…

Good question. In general, all agents should work for both Cloud and Server, even though configuring this for Cloud is certainly much easier due to API keys. I didn’t see any Server user using Vertex agent yet, but I think it should work as long as you configure the Server GraphQL endpoint and GCP service account on the machine from which you start the agent. You can ignore the API key and token in Server, the tenant ID can be set to your default tenant ID

You can ignore the API key and token in Server

As I understand, when you say

ignore

you mean I don’t need to set the values of these two env vars? If these values are not set, when flow running it’ll throw some errors saying that these two env vars need values.

Did you switch to Server?

prefect backend server

Did you switch to Server?

I did, but it threw these following errors. I wonder if it’s a bug when using Server backend

400 List of found errors:	1.Field: job_spec.worker_pool_specs[0].container_spec.env[6].value; Message: Required field is not set.	2.Field: job_spec.worker_pool_specs[0].container_spec.env[5].value; Message: Required field is not set.	 [field_violations {
  field: "job_spec.worker_pool_specs[0].container_spec.env[6].value"
  description: "Required field is not set."
}
field_violations {
  field: "job_spec.worker_pool_specs[0].container_spec.env[5].value"
  description: "Required field is not set."
}
]

I wonder if it’s a bug when using Server backend

Does it mean that you tried with Prefect Cloud and it worked, but with Server it didn’t?

No, I’ve not tried with Prefect Cloud, just had started with Server and it didn’t work.

I could try to reproduce. Can you share more details about what steps did you take? Can you also share the output of the command "prefect diagnostics"?