s/kube-system/services/https:metrics-server:/proxyA similar process is possible with GCR container registries:

zenml service-connector verify gcp-user-account --resource-type docker-registry

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    ┃

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

┃ 🐳 docker-registry │ gcr.io/zenml-core ┃

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

zenml service-connector login gcp-user-account --resource-type docker-registry

Example Command Output

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

WARNING! Your password will be stored unencrypted in /home/stefan/.docker/config.json.

Configure a credential helper to remove this warning. See

https://docs.docker.com/engine/reference/commandline/login/#credentials-store

The 'gcp-user-account' Docker Service Connector connector was used to successfully configure the local Docker/OCI container registry client/SDK.

To verify that the local Docker container registry client is correctly configured, the following command can be used:

docker push gcr.io/zenml-core/zenml-server:connectors

Example Command Output

The push refers to repository [gcr.io/zenml-core/zenml-server]

d4aef4f5ed86: Pushed

2d69a4ce1784: Pushed

204066eca765: Pushed

2da74ab7b0c1: Pushed

75c35abda1d1: Layer already exists

415ff8f0f676: Layer already exists

c14cb5b1ec91: Layer already exists

a1d005f5264e: Layer already exists

3a3fd880aca3: Layer already exists

149a9c50e18e: Layer already exists

1f6d3424b922: Layer already exists

8402c959ae6f: Layer already exists

419599cb5288: Layer already exists

8553b91047da: Layer already exists

connectors: digest: sha256:a4cfb18a5cef5b2201759a42dd9fe8eb2f833b788e9d8a6ebde194765b42fe46 size: 3256