Artifact Registry remote repository

Related topics

• Artifact Registry remote repository is part of Artifact Registry From the official documentation: “This page describes how to create Artifact Registry remote repositories.”
• Artifact Registry remote repository works with container image From the official documentation: “For higher availability, Google recommends deploying these Docker Hub or GitHub Container Registry images using an [Artifact Registry remote repository](/artifact-registry/docs/repositories/remote-repo).”
• Artifact Registry remote repository works with Secret Manager From the official documentation: “In this quickstart, you configure Docker Hub credentials in Secret Manager, create a remote repository, and pull a sample image.”
• Artifact Registry remote repository is an alternative to standard repository From the official documentation: “For standard repositories, you download a package directly from the repository. For a remote repository, you download a cached copy of the package and its dependencies.”
• Artifact Registry remote repository works with virtual repositories From the official documentation: “Use remote repositories together with virtual repositories to mitigate risks associated with public dependencies.”
• Customer-Managed Encryption Keys secures Artifact Registry remote repository From the official documentation: “If you require customer-managed-encryption keys (CMEK) to encrypt repository content, then [create and enable](/artifact-registry/docs/cmek) a key in Cloud KMS for the repository.”
• Customer-Managed Encryption Keys depends on Cloud Key Management Service From the official documentation: “These keys are created and managed using Cloud KMS.”
• Cloud Key Management Service works with Customer-Managed Encryption Keys From the official documentation: “With CMEK, Cloud Key Management Service wraps your stored volume keys.”
• Cloud Run depends on Pub/Sub From the official documentation: “Cloud Run function triggered by Pub/Sub to fetch HYPR MFA logs and write to GCS.”
• Compute Engine is an alternative to GKE From the official documentation: “You can also deploy a third-party model to either Vertex AI Model Garden or self-host on GKE or Compute Engine.”
• Artifact Registry works with Cloud Run From the official documentation: “Cloud Run recommends using Artifact Registry.”
• Customer-Managed Encryption Keys is part of Cloud Key Management Service From the official documentation: “The Cloud KMS keys that you create are customer-managed keys.”
• Pub/Sub works with Secret Manager From the official documentation: “Receive notifications via Pub/Sub when Secret Manager resources change.”
• Compute Engine works with Secret Manager From the official documentation: “To use Secret Manager with workloads running on Compute Engine or GKE, the underlying instance or node must have the `cloud-platform` OAuth scope.”
• Customer-Managed Encryption Keys secures Pub/Sub From the official documentation: “Encrypt Pub/Sub topic with CMEK”
• Artifact Registry works with Google Kubernetes Engine From the official documentation: “You can identify frequently pulled images and copy them to Artifact Registry for deployments to Google Cloud environments such as Google Kubernetes Engine or Cloud Run.”
• Cloud Run is an alternative to GKE From the official documentation: “For your containerized websites, you can also deploy them to [Cloud Run](/run) in addition to [using GKE](#kubernetes-engine).”
• Cloud Run works with Google Kubernetes Engine From the official documentation: “Connecting Cloud Run services to Cloud Service Mesh lets you securely route traffic to workloads on GKE.”
• Cloud Run works with Secret Manager From the official documentation: “The secret is configured to be accessible by Cloud Run and Cloud Build.”
• Compute Engine is an alternative to Google Kubernetes Engine From the official documentation: “You can install MongoDB on a Compute Engine instance or you can deploy MongoDB on Google Kubernetes Engine.”
• GKE depends on Compute Engine From the official documentation: “For example, GKE deploys clusters on Compute Engine VMs.”
• GKE works with Secret Manager From the official documentation: “To use Secret Manager with workloads running on Compute Engine or GKE, the underlying instance or node must have the `cloud-platform` OAuth scope.”
• Artifact Registry works with container image From the official documentation: “Cloud Build then automatically builds your code into a container image and pushes that image to an Artifact Registry [image registry](/run/docs/deploy-functions#image-repository).”
• Artifact Registry works with GKE From the official documentation: “In the next tutorial, you deploy those images from the Artifact Registry repository to a GKE cluster:”
• Cloud Run works with GKE From the official documentation: “Leverage Google Kubernetes Engine (GKE) and Cloud Run to deploy applications to the Google Cloud, optimizing costs, performance, and management overhead.”
• Cloud Run works with Pub/Sub From the official documentation: “A Cloud Run app receives the Pub/Sub message.”
• Customer-Managed Encryption Keys secures Artifact Registry From the official documentation: “Artifact Registry also supports [organization policy constraints](/artifact-registry/docs/cmek#org-policy) that can require CMEK to protect resources.”
• Customer-Managed Encryption Keys secures Compute Engine From the official documentation: “In IL5, CMEK is enabled by default for Compute Engine, Google Kubernetes Engine (GKE), Cloud Storage, and Cloud SQL.”
• Customer-Managed Encryption Keys secures GKE From the official documentation: “CMEKs encrypt data at rest in Cloud SQL, Cloud Storage, and within GKE clusters.”
• Customer-Managed Encryption Keys works with Secret Manager From the official documentation: “In Secret Manager, you can use a CMEK to protect data at rest.”
• Customer-Managed Encryption Keys secures Secret Manager From the official documentation: “You can either create CMEKs manually to protect your Secret Manager resources or use Cloud KMS Autokey.”
• GKE works with Pub/Sub From the official documentation: “GKE publishes upgrade notifications to [Pub/Sub](/pubsub/docs/overview), providing you with a channel to receive information from GKE about your clusters.”
• Google Kubernetes Engine works with Secret Manager From the official documentation: “To use Secret Manager with workloads running on Compute Engine or Google Kubernetes Engine, the underlying instance or node must have the `cloud-platform` OAuth scope.”
• Artifact Registry secures Cloud Run From the official documentation: “You can use Artifact Registry together with other Google Cloud products and features to improve the security posture of developer workflows and tools, software dependencies, CI/CD systems used to build and deploy your software, and runtime environments such as Google Kubernetes…”
• Artifact Registry works with Compute Engine From the official documentation: “Compute Engine can pull containers directly from Artifact Registry repositories so you can run containerized workloads on virtual machine (VM) instances.”
• Artifact Registry secures Google Kubernetes Engine From the official documentation: “You can use Artifact Registry together with other Google Cloud products and features to improve the security posture of developer workflows and tools, software dependencies, CI/CD systems used to build and deploy your software, and runtime environments such as Google Kubernetes…”
• Artifact Registry works with Pub/Sub From the official documentation: “When you activate the Artifact Registry API in a Google Cloud project, Artifact Registry tries to automatically create a Pub/Sub topic with the topic ID `gcr` using Google-owned and Google-managed encryption keys.”
• Artifact Registry works with Secret Manager From the official documentation: “You can store an npm personal access token in Secret Manager and attach it to your remote repository so that Artifact Registry can authenticate upstream requests.”
• Cloud Key Management Service secures Artifact Registry From the official documentation: “[Cloud Key Management Service (Cloud KMS)](/kms) stores the [customer-managed encryption keys (CMEKs)](/kms/docs/cmek) that are used by the services in this blueprint, including your serverless application, Artifact Registry, and Cloud Run functions.”
• Cloud Key Management Service is an alternative to Customer-Managed Encryption Keys From the official documentation: “Unless your control package mandates a certain encryption key strategy, you can use any Google key management service, including Cloud Key Management Service, Cloud External Key Manager, or CMEK.”
• Cloud Key Management Service works with Secret Manager From the official documentation: “If you want to control your encryption keys, then you can use customer-managed encryption keys (CMEKs) in [Cloud KMS](/kms/docs) with CMEK-integrated services including Secret Manager.”
• Cloud Key Management Service is an alternative to Secret Manager From the official documentation: “Secret Manager is the recommended technique for managing sensitive data with Cloud Build. For existing projects, you can continue using Cloud KMS, but for new projects, use Secret Manager.”
• Cloud Run depends on Artifact Registry From the official documentation: “The containerized function is stored in Artifact Registry and deployed to Cloud Run as a service.”
• Cloud Run works with Compute Engine From the official documentation: “This lets Cloud Run clients use this backend service route to send requests directly to Compute Engine instances.”
• Cloud Run works with container image From the official documentation: “**[Use the local configuration of an `app.yaml` file](#appyaml-config) (recommended)**: Choose this option to build a container image directly from your local source code and deploy it to Cloud Run.”
• Cloud Run is an alternative to Google Kubernetes Engine From the official documentation: “**Agent and tool runtimes**: hosting and executing agents or MCP servers on runtimes such as Agent Runtime on Gemini Enterprise Agent Platform, Cloud Run, or Google Kubernetes Engine (GKE) incurs standard compute and runtime charges for those services.”
• Compute Engine works with Google Kubernetes Engine From the official documentation: “Compute Engine integrates with Google Cloud technologies such as Cloud Storage, Google Kubernetes Engine, and BigQuery, to extend beyond the basic computational capability to create more complex and sophisticated applications.”
• container image is part of Artifact Registry From the official documentation: “While Cloud Run doesn't charge when a service isn't in use, you might still be [charged for storing the container image in Artifact Registry](https://cloud.google.com/artifact-registry/pricing).”
• container image depends on Artifact Registry From the official documentation: “You deploy a container image hosted in Artifact Registry.”
• Customer-Managed Encryption Keys secures Cloud Run From the official documentation: “If you want to control your encryption keys, then you can use customer-managed encryption keys (CMEKs) in [Cloud KMS](/kms/docs) with CMEK-integrated services including Cloud Run.”
• Customer-Managed Encryption Keys secures Google Kubernetes Engine From the official documentation: “In IL5, CMEK is enabled by default for Compute Engine, Google Kubernetes Engine (GKE), Cloud Storage, and Cloud SQL.”
• GKE depends on Artifact Registry From the official documentation: “When you create or update a cluster, GKE pulls container images for the Kubernetes system software running on the control plane and nodes from Artifact Registry repositories in the `pkg.dev` or the `gcr.io` domain.”
• Secret Manager secures Cloud Run From the official documentation: “Store sensitive credentials in Secret Manager for secure access by the Cloud Run function.”
• standard repository is part of Artifact Registry From the official documentation: “Create an Artifact Registry standard repository to store your container image:”
• virtual repositories is part of Artifact Registry From the official documentation: “[Virtual repositories](/artifact-registry/docs/repositories/virtual-repo) that aggregate multiple repositories behind a single host.”