ssions, the credentials should include permissionsto connect to and use the GKE cluster (i.e. some or all permissions in the

Kubernetes Engine Developer role).

If set, the resource name must identify an GKE cluster using one of the

following formats:

GKE cluster name: {cluster-name}

GKE cluster names are project scoped. The connector can only be used to access

GKE clusters in the GCP project that it is configured to use.

────────────────────────────────────────────────────────────────────────────────

Displaying information about the service-account GCP authentication method:

zenml service-connector describe-type gcp --auth-method service-account

Example Command Output

╔══════════════════════════════════════════════════════════════════════════════╗

║            🔒 GCP Service Account (auth method: service-account)             ║

╚══════════════════════════════════════════════════════════════════════════════╝

Supports issuing temporary credentials: False

Use a GCP service account and its credentials to authenticate to GCP services.

This method requires a GCP service account and a service account key JSON

created for it.

The GCP connector generates temporary OAuth 2.0 tokens from the user account

credentials and distributes them to clients. The tokens have a limited lifetime

of 1 hour.

A GCP project is required and the connector may only be used to access GCP

resources in the specified project.

If you already have the GOOGLE_APPLICATION_CREDENTIALS environment variable

configured to point to a service account key JSON file, it will be automatically

picked up when auto-configuration is used.

Attributes:

service_account_json {string, secret, required}: GCP Service Account Key JSON

project_id {string, required}: GCP Project ID where the target resource is

located.

────────────────────────────────────────────────────────────────────────────────

Basic Service Connector Types