> For the complete documentation index, see [llms.txt](https://docs.groundcover.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.groundcover.com/customization/customize-deployment/quay.io-registry.md).

# Quay.io registry

The Amazon Elastic Container Registry (ECR) Public Registry Pull Bandwidth Limit for clusters outside of AWS is set to 500 GB per day. This means that, collectively, all container image pulls from ECR Public by all clusters located outside the AWS network cannot exceed 500 GB of data transfer in a 30 days period.

It is crucial for users who operate Kubernetes clusters or other container orchestrators outside of AWS and use ECR Public as a container image source to be aware of this bandwidth limitation. If the cumulative data transfer of container image pulls from ECR Public exceeds the daily limit, further pulls may be denied until the bandwidth usage falls back within the allowed threshold.

To address potential bandwidth limitations with Amazon ECR Public when using clusters outside of the AWS network, one viable solution is to override the container registry to utilize an alternative registry, such as Quay.io. By redirecting the container image pulls to Quay.io, users can leverage the bandwidth allowance and performance capabilities of Quay.io to complement or replace ECR Public for image retrieval.

### Override Registry to quay.io

{% tabs %}
{% tab title="Using CLI" %}

```bash

# if you have helm overrides file, you can pass it using `-f <overrides>.yaml`
groundcover deploy --registry quay
```

{% endtab %}

{% tab title="Using Helm" %}

```bash

# Upgrade groundcover release
helm get values -n groundcover groundcover -o yaml | \
helm upgrade \
    groundcover \
    groundcover/groundcover \
    -n groundcover \
    -f - \
    -f https://raw.githubusercontent.com/groundcover-com/cli/main/pkg/helm/presets/quay.yaml
```

{% endtab %}
{% endtabs %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.groundcover.com/customization/customize-deployment/quay.io-registry.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.