<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Registry on</title><link>https://deploy-preview-3050--ornate-narwhal-088216.netlify.app/tags/registry/</link><description>Recent content in Registry on</description><generator>Hugo -- gohugo.io</generator><language>en-US</language><lastBuildDate>Mon, 08 Jul 2024 15:56:52 -0700</lastBuildDate><atom:link href="https://deploy-preview-3050--ornate-narwhal-088216.netlify.app/tags/registry/index.xml" rel="self" type="application/rss+xml"/><item><title>How to Set Up Pull Through from Chainguard's Registry to Google Artifact Registry</title><link>https://deploy-preview-3050--ornate-narwhal-088216.netlify.app/chainguard/chainguard-images/chainguard-registry/pull-through-guides/artifact-registry-pull-through/</link><pubDate>Mon, 08 Jul 2024 15:56:52 -0700</pubDate><guid>https://deploy-preview-3050--ornate-narwhal-088216.netlify.app/chainguard/chainguard-images/chainguard-registry/pull-through-guides/artifact-registry-pull-through/</guid><description>Organizations can use Chainguard Containers along with third-party software repositories in order to integrate with current workflows as the single source of truth for software artifacts. In this situation, you can set up a proxy repository to function as a mirror of Chainguard&amp;rsquo;s registry. This mirror can then serve as a pull through cache for your Chainguard Containers.
This tutorial outlines how to set up a remote repository with Google Artifact Registry.</description></item><item><title>Registry Overview</title><link>https://deploy-preview-3050--ornate-narwhal-088216.netlify.app/chainguard/chainguard-images/chainguard-registry/overview/</link><pubDate>Tue, 21 Mar 2023 16:36:47 +0000</pubDate><guid>https://deploy-preview-3050--ornate-narwhal-088216.netlify.app/chainguard/chainguard-images/chainguard-registry/overview/</guid><description>Chainguard Registry hosts more secure container images with two access tiers: public Free images available to everyone, and production images that require authentication for enterprise features like SLAs and version pinning. The registry integrates with standard container tools while providing enhanced security through signed images and comprehensive metadata.
While all public Chainguard Containers are freely available, logging in with a Chainguard account and authenticating when pulling from the registry provides a mechanism for Chainguard to contact you if there are any current or known upcoming issues with images you are pulling.</description></item><item><title>Authenticate to Chainguard's Registry</title><link>https://deploy-preview-3050--ornate-narwhal-088216.netlify.app/chainguard/chainguard-images/chainguard-registry/authenticating/</link><pubDate>Tue, 21 Mar 2023 15:10:16 +0000</pubDate><guid>https://deploy-preview-3050--ornate-narwhal-088216.netlify.app/chainguard/chainguard-images/chainguard-registry/authenticating/</guid><description>Public Container Images Chainguard offers a collection of images that are publicly available, don&amp;rsquo;t require authentication, and are free to use by anyone. However, logging in with a Chainguard account and authenticating when pulling from the registry gives you access to the Chainguard Console, and provides a mechanism for Chainguard to contact you if there are any issues with images you are pulling. This may enable Chainguard to notify you of upcoming deprecations, changes in behavior, critical vulnerabilities and remediations for images you have recently pulled.</description></item></channel></rss>