Integrations / Google Artifact Registry

Google Artifact Registry

Every container image pull from Cloud Run, GKE, and other Google Cloud services routes directly to JFrog Artifactory as it happens, with no caching layer in between.
Start Free Book a Demo

Google Artifact Registry Integration Features

Single Source of Truth for Production

JFrog Artifactory remains the authoritative source for every container image, even for workloads running on Cloud Run and Google Kubernetes Engine (GKE). The Artifact Registry Connector forwards each request live to JFrog Artifactory, so the image a workload pulls through Google Artifact Registry is exactly the image JFrog Artifactory has under management at that moment.

Real-Time Policy Enforcement on Every Pull

Security policies apply at the moment of the request, not just at build time. When a new critical CVE is discovered on an image already in production, blocking it in JFrog Artifactory blocks the next pull from Cloud Run or GKE immediately, with no configuration changes needed on the Google Cloud side.

Passthrough Architecture, No Lag

The Artifact Registry Connector is a passthrough proxy by design. Because no copy of the image is stored in Google Artifact Registry, there is no gap between an update in JFrog Artifactory and what your workloads pull. Every request routes live, keeping governance intact end to end.

A Familiar Pull Pattern for Google Cloud Workloads

Cloud Run, GKE, and other Google Cloud services can pull from JFrog Artifactory the same way they pull from any Artifact Registry repository. No new agent, no runtime dependency, no changes to how developers deploy.

A Simpler Delivery Pipeline

The scheduled sync jobs, mirrored repositories, and custom Cloud Functions that teams have historically used to bridge JFrog Artifactory and Google Artifact Registry can retire. A single Artifact Registry Connector repository replaces the workaround stack with a supported, governed integration.

Related Resources
Documentation

Integration Documentation

Read
Blog

JFrog Artifactory Now Integrates Natively with Artifact Registry in Google Cloud

Read
Documentation

Connector Repositories Overview

Read

Frequently Asked Questions

How is the Google Artifact Registry Connector different from a standard remote repository?

The Artifact Registry Connector is purpose-built as a passthrough proxy: it stores no copy of the image, and every request is forwarded live to JFrog Artifactory so governance and policy enforcement stay intact in real time. Standard remote repositories cache upstream artifacts locally, which is the right pattern for many use cases but places a copy outside JFrog Artifactory’s governance model when JFrog Artifactory is your authoritative registry.

Which Google Cloud services can pull from JFrog Artifactory through the Artifact Registry Connector?

Any Google Cloud service that consumes container images from Google Artifact Registry can pull through the Artifact Registry Connector, including Cloud Run and Google Kubernetes Engine. From the workload’s perspective, the Artifact Registry Connector looks like a standard Artifact Registry repository, so no changes are needed to your deployment tooling.

About Google Artifact Registry

Google Artifact Registry is Google Cloud's managed service for storing, managing, and securing container images and language packages. The Artifact Registry Connector repository mode extends Artifact Registry with a passthrough proxy pattern that links Google Cloud runtime services directly to trusted upstream registries in real time.
Learn More