D Kubernetes clusters and local Docker containers.when used with a remote ZenML server, the implicit authentication method only works if your ZenML server is deployed in the same cloud as the one supported by the Service Connector Type that you are using. For instance, if you're using the AWS Service Connector Type, then the ZenML server must also be deployed in AWS (e.g. in an EKS Kubernetes cluster). You may also need to manually adjust the cloud configuration of the remote cloud workload where the ZenML server is running to allow access to resources (e.g. add permissions to the AWS IAM role attached to the EC2 or EKS node, add roles to the GCP service account attached to the GKE cluster nodes).

The following is an example of using the GCP Service Connector's implicit authentication method to gain immediate access to all the GCP resources that the ZenML server also has access to. Note that this is only possible because the ZenML server is also deployed in GCP, in a GKE cluster, and the cluster is attached to a GCP service account with permissions to access the project resources:

zenml service-connector register gcp-implicit --type gcp --auth-method implicit --project_id=zenml-core

Example Command Output

Successfully registered service connector `gcp-implicit` with access to the following resources:

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

┃     RESOURCE TYPE     │ RESOURCE NAMES                                  ┃

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

┃    🔵 gcp-generic     │ zenml-core                                      ┃

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

┃     📦 gcs-bucket     │ gs://annotation-gcp-store                       ┃

┃                       │ gs://zenml-bucket-sl                            ┃

┃                       │ gs://zenml-core.appspot.com                     ┃

┃                       │ gs://zenml-core_cloudbuild                      ┃