From ea10aa8ef93f9a4486d2f1a28675d13f68d42fe7 Mon Sep 17 00:00:00 2001
From: Aviral Takkar <avtakkar@microsoft.com>
Date: Tue, 21 May 2024 08:53:59 -0700
Subject: [PATCH] docs: update readme

---
 README.md | 10 ++--------
 1 file changed, 2 insertions(+), 8 deletions(-)

diff --git a/README.md b/README.md
index b61b097..f530290 100644
--- a/README.md
+++ b/README.md
@@ -82,14 +82,8 @@ CLUSTER_CONTEXT=<your-cluster-context> && \
     --set peerd.image.ref=ghcr.io/azure/acr/dev/peerd:stable
 ```
 
-By default, some well known registries are mirrored (see [values.yml]), but this is configurable. For example, to mirror
-`docker.io`, `mcr.microsoft.com` and `ghcr.io`, run the following.
-
-```bash
-CLUSTER_CONTEXT=<your-cluster-context> && \
-  helm --kube-context=$CLUSTER_CONTEXT install --wait peerd ./build/package/peerd-helm \
-    --set peerd.image.ref=ghcr.io/azure/acr/dev/peerd:stable
-```
+By default, some well known registries are mirrored, but this is configurable using the [values.yml] file.
+Update the `peerd.hosts` field to include the registries you want to mirror.
 
 On deployment, each Peerd instance will try to connect to its peers in the cluster.