        │        │         │            │        ┃┗━━━━━━━━┷━━━━━━━━━━━━━━━━━━┷━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┷━━━━━━━━┷━━━━━━━━━━━━━━━━━━━━━━━┷━━━━━━━━━━━━━━━┷━━━━━━━━┷━━━━━━━━━┷━━━━━━━━━━━━┷━━━━━━━━┛

The following lists all Kubernetes clusters accessible through the GCP Service Connector:

zenml service-connector verify gcp-user-account --resource-type kubernetes-cluster

Example Command Output

Service connector 'gcp-user-account' is correctly configured with valid credentials and has access to the following resources:

┏━━━━━━━━━━━━━━━━━━━━━━━┯━━━━━━━━━━━━━━━━━━━━┓

┃     RESOURCE TYPE     │ RESOURCE NAMES     ┃

┠───────────────────────┼────────────────────┨

┃ 🌀 kubernetes-cluster │ zenml-test-cluster ┃

┗━━━━━━━━━━━━━━━━━━━━━━━┷━━━━━━━━━━━━━━━━━━━━┛

Calling the login CLI command will configure the local Kubernetes kubectl CLI to access the Kubernetes cluster through the GCP Service Connector:

zenml service-connector login gcp-user-account --resource-type kubernetes-cluster --resource-id zenml-test-cluster

Example Command Output

⠴ Attempting to configure local client using service connector 'gcp-user-account'...

Context "gke_zenml-core_zenml-test-cluster" modified.

Updated local kubeconfig with the cluster details. The current kubectl context was set to 'gke_zenml-core_zenml-test-cluster'.

The 'gcp-user-account' Kubernetes Service Connector connector was used to successfully configure the local Kubernetes cluster client/SDK.

To verify that the local Kubernetes kubectl CLI is correctly configured, the following command can be used:

kubectl cluster-info

Example Command Output

Kubernetes control plane is running at https://35.185.95.223

GLBCDefaultBackend is running at https://35.185.95.223/api/v1/namespaces/kube-system/services/default-http-backend:http/proxy

KubeDNS is running at https://35.185.95.223/api/v1/namespaces/kube-system/services/kube-dns:dns/proxy

Metrics-server is running at https://35.185.95.223/api/v1/namespaces/kube-system/services/https:metrics-server:/proxy