Google Cloud Container Registry
Storing container images in GCP.
When to use it
You should use the GCP container registry if:
one or more components of your stack need to pull or push container images.
How to deploy it
Infrastructure Deployment
A GCP Container Registry can be deployed directly from the ZenML CLI:
How to find the registry URI
When using the Google Container Registry, the GCP container registry URI should have one of the following formats:
To figure out the URI for your registry:
Click on the dropdown menu in the top left to get a list of available projects with their names and IDs.
Use the ID of the project you want to use fill in the template
gcr.io/<PROJECT_ID>
and get your URI (You can also use the other prefixes<us/eu/asia>.gcr.io
as explained above if you want your images stored in a different region).
Infrastructure Deployment
A GCP Container Registry can be deployed directly from the ZenML CLI:
You can pass other configurations specific to the stack components as key-value arguments. If you don't provide a name, a random one is generated for you. For more information about how to work use the CLI for this, please refer to the dedicated documentation section.
How to use it
To use the GCP container registry, we need:
We can then register the container registry and use it in our active stack:
Authentication Methods
With the GCP CLI installed and set up with credentials, we'll need to configure Docker, so it can pull and push images:
for a Google Container Registry:
for a Google Artifact Registry:
Last updated