# Hosting Linkerd2 images in an ECR pull-through cache compatible registry

**URL:** <https://linkerd.buoyant.io/t/hosting-linkerd2-images-in-an-ecr-pull-through-cache-compatible-registry/155>\
**Category:** Linkerd General Discussion\
**Created:** [June 6, 2023, 1:31pm UTC](https://linkerd.buoyant.io/t/hosting-linkerd2-images-in-an-ecr-pull-through-cache-compatible-registry/155 "2023-06-06T13:31:01Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![jmorganwalker](https://avatars.discourse-cdn.com/v4/letter/j/a8b319/32.png) [@jmorganwalker](https://linkerd.buoyant.io/u/jmorganwalker)\
**Post date:** [June 6, 2023, 1:31pm UTC](https://linkerd.buoyant.io/t/hosting-linkerd2-images-in-an-ecr-pull-through-cache-compatible-registry/155/1 "2023-06-06T13:31:01Z")

</div>

Hello! I was wondering if there were any plans of hosting Linkerd2 images on ECR Public or another ECR pull-through cache compatible registry like quay or [registry.k8s.io](http://registry.k8s.io). As we’re all aware, Linkerd acts as a backbone to many of our k8s workloads and if we’re unable to pull those images, e.g. during this [4/27 Github outage](https://www.githubstatus.com/incidents/vsc464zj7gv4), a production outage is imminent.

I understand we can use our own private registry but that brings along more operational overhead to set up an automated process to routinely pull down the latest linkerd images and push them to our own registries.

---

<div class="post-metadata">

**Author:** ![william](https://yyz1.discourse-cdn.com/flex029/user_avatar/linkerd.buoyant.io/william/32/5_2.png) [@william](https://linkerd.buoyant.io/u/william)\
**Post date:** [June 8, 2023, 6:53pm UTC](https://linkerd.buoyant.io/t/hosting-linkerd2-images-in-an-ecr-pull-through-cache-compatible-registry/155/2 "2023-06-08T18:53:34Z")

</div>

Hi @jmorganwalker! Unfortunately we don’t have any plans to move beyond GHCR for hosting of open source Linkerd images.

Of course anyone is welcome to set up such a registry for the community. I’ll also note that Buoyant does provide some alternatives for its enterprise Linkerd customers, but ultimately even in those cases we strongly encourage production users to set up a local registry that they have control over rather than incurring a unnecessary deploy-time dependency.

---

<div class="post-metadata">

**Author:** ![jmorganwalker](https://avatars.discourse-cdn.com/v4/letter/j/a8b319/32.png) [@jmorganwalker](https://linkerd.buoyant.io/u/jmorganwalker)\
**Post date:** [June 12, 2023, 3:14pm UTC](https://linkerd.buoyant.io/t/hosting-linkerd2-images-in-an-ecr-pull-through-cache-compatible-registry/155/3 "2023-06-12T15:14:17Z")

</div>

Thanks for the follow-up, William. We’ll continue to investigate our options.