Skip to content

Commit

Permalink
Adding recommendation to Registry Overview (#2042)
Browse files Browse the repository at this point in the history
[ ] Check if this is a typo or other quick fix and ignore the rest :)

## Type of change
<!-- Please be sure to add the appropriate label to your PR. -->
We don't offer an SLA for cgr.dev, this pr adds this info to the
registry overview and includes a recommendation that customers use a
pull through proxy for maximum reliability.

### What should this PR do?
<!-- Does this PR resolve an issue? Please include a reference to it.
-->
Resolves chainguard-dev/internal#4572

### Why are we making this change?
<!-- What larger problem does this PR address? -->

### What are the acceptance criteria? 
<!-- What should be happening for this PR to be accepted? Please list
criteria. -->
<!-- Do any stakeholders need to be tagged in this review? If so, please
add them. -->

### How should this PR be tested?
<!-- What should your reviewer do to test this PR? Please list steps.
-->
This is a fairly small update but should be reviewed for clarity.

Relevant preview link:
https://deploy-preview-2042--ornate-narwhal-088216.netlify.app/chainguard/chainguard-registry/overview/

Signed-off-by: Mark Drake <[email protected]>
  • Loading branch information
SharpRake authored Jan 27, 2025
1 parent a057b1c commit 0c63cef
Showing 1 changed file with 11 additions and 0 deletions.
11 changes: 11 additions & 0 deletions content/chainguard/chainguard-registry/overview.md
Original file line number Diff line number Diff line change
Expand Up @@ -27,3 +27,14 @@ You can check the status of the Chainguard Registry at [https://status.cgr.dev](
## Network Requirements

Refer to our [Chainguard Images Network Requirements](/chainguard/administration/network-requirements) reference page for details about how to ensure access to Chainguard Registry in environments using firewalls, access control lists, and proxies.

## Using a Caching Proxy with the Chainguard Registry

Chainguard does not offer an SLA for uptime for the Chaingaurd Registry. In order to minimize production dependency on the Chainguard Registry, we recommend that customers use a pull-through proxy for maximum reliability.

We currently provide documentation on how you can set up a pull-through cache for the Chainguard Registry on the following platforms:

* [Google Artifact Registry](/chainguard/chainguard-registry/pull-through-guides/artifact-registry-pull-through/)
* [JFrog Artifactory](/chainguard/chainguard-registry/pull-through-guides/artifactory/)
* [Sonatype Nexus](/chainguard/chainguard-registry/pull-through-guides/nexus-pull-through/)
* [Cloudsmith](/chainguard/chainguard-registry/pull-through-guides/cloudsmith-pull-through/)

0 comments on commit 0c63cef

Please sign in to comment.