--- title: JFrog Artifactory Now Integrates Natively with Artifact... description: Google Artifact Registry now supports a new repository mode called Connector, which acts as a real-time passthrough proxy to private registries like JFrog... canonical: https://daily.dev/posts/jfrog-artifactory-now-integrates-natively-with-artifact-registry-in-google-cloud-urj3tnbzz twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: JFrog Artifactory Now Integrates Natively with Artifact Registry in Google Cloud | daily.dev og:description: Google Artifact Registry now supports a new repository mode called Connector, which acts as a real-time passthrough proxy to private registries like JFrog... og:url: https://daily.dev/posts/jfrog-artifactory-now-integrates-natively-with-artifact-registry-in-google-cloud-urj3tnbzz og:image: https://api.daily.dev/og/posts/urj3TNbZz.png og:image:alt: JFrog Artifactory Now Integrates Natively with Artifact Registry in Google Cloud og:image:width: 1200 og:image:height: 630 og:locale: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # JFrog Artifactory Now Integrates Natively with Artifact Registry in Google Cloud **[JFrog](https://daily.dev/sources/jfrog)** · 6 min read · 0 upvotes · 0 comments ## Summary Google Artifact Registry now supports a new repository mode called Connector, which acts as a real-time passthrough proxy to private registries like JFrog Artifactory. Instead of syncing or mirroring container images between JFrog and Artifact Registry, every image pull from Cloud Run or GKE is forwarded live to JFrog Artifactory, which serves the image and enforces security policy at the moment of the pull. This removes the need for scheduled sync jobs, custom Cloud Functions, or maintaining two registries, and ensures newly discovered critical CVEs can block image pulls immediately, even for previously approved images. Setup involves creating a JFrog Docker repository, storing an access token in Google Secret Manager, configuring a Connector-mode repository in Artifact Registry, and pointing workloads at it. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Questions this post answers ### What is the Artifact Registry Connector in Google Cloud and how does it work with JFrog Artifactory? The Artifact Registry Connector is a new repository mode in Google Artifact Registry that acts as a real-time passthrough proxy to a private registry like JFrog Artifactory, forwarding every image pull request directly to JFrog without storing a copy in Artifact Registry. This lets Cloud Run and GKE pull images while JFrog retains full policy enforcement, blocking pulls immediately if a critical CVE is discovered. _daily.dev helps teams track new registry integrations like this as they roll out across cloud platforms._ ### How do I set up JFrog Artifactory as the upstream source for a Google Artifact Registry Connector repository? Create a dedicated virtual Docker repository in JFrog Artifactory and note its URL, then store a JFrog access token in Google Secret Manager (ideally using the JFrog GCP Secret Rotator for auto-rotation). Next, create a new Artifact Registry repository in Connector mode pointing to the JFrog URL with the secret, then reference it from Cloud Run or GKE like any other Artifact Registry repository. _engineers wiring up cloud registries can follow config walkthroughs like this via daily.dev._ ### Why would a team avoid syncing container images between JFrog Artifactory and Google Artifact Registry? Syncing images on a schedule, using custom Cloud Functions to mirror on push, or maintaining two registries in parallel introduces cache lag, divergence risk, and operational overhead, and none of these approaches preserve real-time policy enforcement. A passthrough connector avoids storing a second copy, so every pull is always current and subject to Artifactory's active security policy at request time. _daily.dev surfaces architecture tradeoffs like registry syncing for teams comparing artifact management setups._ ## Similar posts on daily.dev - [The Power of JFrog Artifactory as Your Model Registry](https://daily.dev/posts/the-power-of-jfrog-artifactory-as-your-model-registry-f3dnsbhl9) · JFrog · 0 upvotes · 0 comments - [Harness Reimagines Artifact Management for DevSecOps with New Artifact Registry](https://daily.dev/posts/harness-reimagines-artifact-management-for-devsecops-with-new-artifact-registry-wibc3pc54) · InfoQ · 0 upvotes · 0 comments - [Every artifact your teams ship, assembled right the first time](https://daily.dev/posts/every-artifact-your-teams-ship-assembled-right-the-first-time-vom1zsrhb) · GitLab · 0 upvotes · 0 comments - [Introducing JFrog Fly: The World’s First Agentic Artifact Repository](https://daily.dev/posts/introducing-jfrog-fly-the-world-s-first-agentic-artifact-repository-0u3vkypqj) · JFrog · 0 upvotes · 0 comments --- Tags: [#containers](https://daily.dev/tags/containers), [#gcp](https://daily.dev/tags/gcp), [#devsecops](https://daily.dev/tags/devsecops) [View this post on daily.dev](https://daily.dev/posts/jfrog-artifactory-now-integrates-natively-with-artifact-registry-in-google-cloud-urj3tnbzz) ```json {"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]} {"@context":"https://schema.org","@type":"TechArticle","headline":"JFrog Artifactory Now Integrates Natively with Artifact Registry in Google Cloud","url":"https://daily.dev/posts/jfrog-artifactory-now-integrates-natively-with-artifact-registry-in-google-cloud-urj3tnbzz","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/jfrog-artifactory-now-integrates-natively-with-artifact-registry-in-google-cloud-urj3tnbzz"},"datePublished":"2026-08-12T13:35:05.154Z","dateModified":"2026-08-12T13:35:37.074Z","description":"Google Artifact Registry now supports a new repository mode called Connector, which acts as a real-time passthrough proxy to private registries like JFrog...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/f019c0137b196b72a961c1ee84377182?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/f019c0137b196b72a961c1ee84377182?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"JFrog","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"JFrog","logo":"https://media.daily.dev/image/upload/t_logo,f_auto/v1/logos/b11bf37102384ac9983be701b2cf7cd5","url":"https://daily.dev/sources/jfrog"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/jfrog-artifactory-now-integrates-natively-with-artifact-registry-in-google-cloud-urj3tnbzz","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"containers,gcp,devsecops","timeRequired":"PT6M"} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"JFrog","item":"https://daily.dev/sources/jfrog"},{"@type":"ListItem","position":3,"name":"JFrog Artifactory Now Integrates Natively with Artifact Registry in Google Cloud"}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/jfrog-artifactory-now-integrates-natively-with-artifact-registry-in-google-cloud-urj3tnbzz#faq","mainEntity":[{"@type":"Question","name":"What is the Artifact Registry Connector in Google Cloud and how does it work with JFrog Artifactory?","acceptedAnswer":{"@type":"Answer","text":"The Artifact Registry Connector is a new repository mode in Google Artifact Registry that acts as a real-time passthrough proxy to a private registry like JFrog Artifactory, forwarding every image pull request directly to JFrog without storing a copy in Artifact Registry. This lets Cloud Run and GKE pull images while JFrog retains full policy enforcement, blocking pulls immediately if a critical CVE is discovered. daily.dev helps teams track new registry integrations like this as they roll out across cloud platforms."}},{"@type":"Question","name":"How do I set up JFrog Artifactory as the upstream source for a Google Artifact Registry Connector repository?","acceptedAnswer":{"@type":"Answer","text":"Create a dedicated virtual Docker repository in JFrog Artifactory and note its URL, then store a JFrog access token in Google Secret Manager (ideally using the JFrog GCP Secret Rotator for auto-rotation). Next, create a new Artifact Registry repository in Connector mode pointing to the JFrog URL with the secret, then reference it from Cloud Run or GKE like any other Artifact Registry repository. engineers wiring up cloud registries can follow config walkthroughs like this via daily.dev."}},{"@type":"Question","name":"Why would a team avoid syncing container images between JFrog Artifactory and Google Artifact Registry?","acceptedAnswer":{"@type":"Answer","text":"Syncing images on a schedule, using custom Cloud Functions to mirror on push, or maintaining two registries in parallel introduces cache lag, divergence risk, and operational overhead, and none of these approaches preserve real-time policy enforcement. A passthrough connector avoids storing a second copy, so every pull is always current and subject to Artifactory's active security policy at request time. daily.dev surfaces architecture tradeoffs like registry syncing for teams comparing artifact management setups."}}]} ```