From d8827c26c95eff769ccbd9a1bc2197efb78a02f3 Mon Sep 17 00:00:00 2001 From: Giuseppe Capizzi Date: Mon, 23 Jan 2023 16:56:11 +0000 Subject: [PATCH] Improve registry-related instructions * `--docker-server` already defaults to DockerHub; * GCR is deprecated, mention GAR instead; * spell out acronyms. --- INSTALL.md | 22 +++++++++++----------- 1 file changed, 11 insertions(+), 11 deletions(-) diff --git a/INSTALL.md b/INSTALL.md index 39b3ebcf1..e4c4f0a6d 100644 --- a/INSTALL.md +++ b/INSTALL.md @@ -113,13 +113,13 @@ kubectl --namespace "$ROOT_NAMESPACE" create secret docker-registry image-regist Make sure the value of `--docker-server` is a valid [URI authority](https://datatracker.ietf.org/doc/html/rfc3986#section-3.2). - If using **DockerHub**: - - `--docker-server` should be `https://index.docker.io/v1/`; + - `--docker-server` should be omitted; - `--docker-username` should be your DockerHub user; - `--docker-password` can be either your DockerHub password or a [generated personal access token](https://hub.docker.com/settings/security?generateToken=true). -- If using **GCR**: - - `--docker-server` should be `gcr.io`; +- If using **Google Artifact Registry**: + - `--docker-server` should be `-docker.pkg.dev`; - `--docker-username` should be `_json_key`; - - `--docker-password` should be the JSON-formatted access token for a service account that has permission to manage images in GCR. + - `--docker-password` should be the JSON-formatted access token for a service account that has permission to manage images in Google Artifact Registry. ### TLS certificates @@ -170,13 +170,13 @@ helm install korifi https://github.com/cloudfoundry/korifi/releases/download/v.azurecr.io/foo/bar/korifi-` | `.azurecr.io/foo/bar/korifi--packages` | Repositories are created dynamically during push by ACR | -| DockerHub | `index.docker.io//` | `index.docker.io//-packages` | Docker does not support nested repositories | -| ECR | `.dkr.ecr..amazonaws.com/foo/bar/korifi-` | `.dkr.ecr..amazonaws.com/foo/bar/korifi--packages` | Korifi will create the repository before pushing, as dynamic repository creation is not posssible on ECR | -| GAR | `-docker.pkg.dev//foo/bar/korifi-` | `-docker.pkg.dev//foo/bar/korifi--packages` | The `foo` repository must already exist in GAR | -| GCR | `gcr.io//foo/bar/korifi-` | `gcr.io//foo/bar/korifi--packages` | Repositories are created dynamically during push by GCR | +| Registry | containerRepositoryPrefix | Resultant Image Ref | Notes | +| --------------------------------- | ------------------------------------------------------------ | ------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------- | +| Azure Container Registry | `.azurecr.io/foo/bar/korifi-` | `.azurecr.io/foo/bar/korifi--packages` | Repositories are created dynamically during push by ACR | +| DockerHub | `index.docker.io//` | `index.docker.io//-packages` | Docker does not support nested repositories | +| Amazon Elastic Container Registry | `.dkr.ecr..amazonaws.com/foo/bar/korifi-` | `.dkr.ecr..amazonaws.com/foo/bar/korifi--packages` | Korifi will create the repository before pushing, as dynamic repository creation is not posssible on ECR | +| Google Artifact Registry | `-docker.pkg.dev//foo/bar/korifi-` | `-docker.pkg.dev//foo/bar/korifi--packages` | The `foo` repository must already exist in GAR | +| Google Container Registry | `gcr.io//foo/bar/korifi-` | `gcr.io//foo/bar/korifi--packages` | Repositories are created dynamically during push by GCR | The chart provides various other values that can be set. See [`README.helm.md`](./README.helm.md) for details.