Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

docs: update readme #49

Merged
merged 1 commit into from
May 21, 2024
Merged

docs: update readme #49

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 2 additions & 8 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.

Expand Down
Loading