━━━━━━━━┯━━━━━━━━━━━━━━━━━━━━┯━━━━━━━━━━━━━━━━━━━┓┃             CONNECTOR ID             │ CONNECTOR NAME   │ CONNECTOR TYPE │ RESOURCE TYPE      │ RESOURCE NAMES    ┃

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

┃ ffc01795-0c0a-4f1d-af80-b84aceabcfcf │ gcp-implicit     │ 🔵 gcp         │ 🐳 docker-registry │ gcr.io/zenml-core ┃

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

┃ 561b776a-af8b-491c-a4ed-14349b440f30 │ gcp-zenml-core   │ 🔵 gcp         │ 🐳 docker-registry │ gcr.io/zenml-core ┃

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

After having set up or decided on a GCP Service Connector to use to connect to the target GCR registry, you can register the GCP Container Registry as follows:

# Register the GCP container registry and reference the target GCR registry URI

zenml container-registry register <CONTAINER_REGISTRY_NAME> -f gcp \

--uri=<REGISTRY_URL>

# Connect the GCP container registry to the target GCR registry via a GCP Service Connector

zenml container-registry connect <CONTAINER_REGISTRY_NAME> -i

A non-interactive version that connects the GCP Container Registry to a target GCR registry through a GCP Service Connector:

zenml container-registry connect <CONTAINER_REGISTRY_NAME> --connector <CONNECTOR_ID>

Linking the GCP Container Registry to a Service Connector means that your local Docker client is no longer authenticated to access the remote registry. If you need to manually interact with the remote registry via the Docker CLI, you can use the local login Service Connector feature to temporarily authenticate your local Docker client to the remote registry:

zenml service-connector login <CONNECTOR_NAME> --resource-type docker-registry

Example Command Output

$ zenml service-connector login gcp-zenml-core --resource-type docker-registry