Some of your production services are running in Google Kubernetes Engine (GKE) in the eu-west-1 region.
Your build system runs in the us-west-1 region.
You want to push the container images from your build system to a scalable registry to maximize the bandwidth for transferring the images to the cluster.
What should you do?
Click on the arrows to vote for the correct answer
A. B. C. D.B.
https://cloud.google.com/container-registry/docs/pushing-and-pullingTo push container images from the build system in us-west-1 region to a scalable registry for the production services running in GKE in eu-west-1 region, we need to consider the following options:
A. Push the images to Google Container Registry (GCR) using the gcr.io hostname: This option is valid because Google Container Registry (GCR) is a scalable and secure container image registry that allows you to store, manage, and deploy Docker container images. GCR has high bandwidth connectivity to GKE clusters in all regions, including eu-west-1. Therefore, pushing the images to GCR using the gcr.io hostname is a valid option.
B. Push the images to Google Container Registry (GCR) using the us.gcr.io hostname: This option is not valid because using the us.gcr.io hostname means that the images will be stored in a region that is geographically distant from the GKE cluster, which will increase the latency and reduce the bandwidth for transferring the images to the eu-west-1 region.
C. Push the images to Google Container Registry (GCR) using the eu.gcr.io hostname: This option is valid because eu.gcr.io is a regional endpoint for GCR in the eu-west-1 region. However, pushing the images to eu.gcr.io may not provide the maximum bandwidth for transferring the images to the GKE cluster in the same region because GCR has high bandwidth connectivity to GKE clusters in all regions, including eu-west-1.
D. Push the images to a private image registry running on a Compute Engine instance in the eu-west-1 region: This option is not valid because it requires setting up and maintaining a private image registry, which may not be as scalable and secure as GCR. Moreover, pushing images to a private registry may not provide the maximum bandwidth for transferring the images to the GKE cluster in the same region as compared to using GCR.
Therefore, the best option for pushing container images from the build system in us-west-1 region to a scalable registry for the production services running in GKE in eu-west-1 region is to push the images to Google Container Registry (GCR) using the gcr.io hostname.