Config Sync mithilfe einer privaten Registry aktualisieren

Für jede Version von Config Sync muss ein bestimmter Satz von versionierten Images ausgeführt werden. Wenn Sie eine private Registry verwenden, müssen Sie diese Images per Pull, Tag und Push in die private Registry verschieben, bevor Sie Config Sync-Komponenten installieren oder ein Upgrade der Config Sync-Version ausführen können.

Hinweis :Eine private Registry wird im Rahmen der Einrichtung des Administratorclusters für Google Distributed Cloud konfiguriert. Config Sync erkennt automatisch, wenn eine private Registry konfiguriert wurde, und stellt sicher, dass die private Registry von Config Sync verwendet wird. Weitere Informationen finden Sie in der Google Distributed Cloud-Dokumentation unter Administratorcluster erstellen.

Images zu einer privaten Registry hinzufügen

Klicken Sie auf das Plussymbol für die Version, die Sie verwenden möchten, und führen Sie die aufgeführten Schritte aus, um versionsspezifische Config Sync Images in eine private Registry zu senden.

Hinweis: Verwenden Sie einen Client, von dem Sie Daten aus gcr.io abrufen und in Ihre private Registry senden können.

1.22.2

Führen Sie die folgenden Schritte aus, um die Images zu einer privaten Registry hinzuzufügen:

1. Rufen Sie die Config Sync-Images ab:

   docker pull gcr.io/config-management-release/admission-webhook:v1.22.2-rc.1
   docker pull gcr.io/config-management-release/gcenode-askpass-sidecar:v1.22.2-rc.1
   docker pull gcr.io/config-management-release/git-sync:v4.4.2-gke.3__linux_amd64
   docker pull gcr.io/config-management-release/helm-sync:v1.22.2-rc.1
   docker pull gcr.io/config-management-release/hydration-controller:v1.22.2-rc.1
   docker pull gcr.io/config-management-release/oci-sync:v1.22.2-rc.1
   docker pull gcr.io/config-management-release/otelcontribcol:v0.119.0-gke.2
   docker pull gcr.io/config-management-release/reconciler-manager:v1.22.2-rc.1
   docker pull gcr.io/config-management-release/reconciler:v1.22.2-rc.1
   docker pull gcr.io/config-management-release/resource-group-controller:v1.22.2-rc.1
   

2. Erstellen Sie eine Variable für Ihre private Registry-URL:

   export PRIVATE_REGISTRY_URL=PRIVATE_REGISTRY_URL
   

   Ersetzen Sie PRIVATE_REGISTRY_URL durch Ihre private Registry-URL.
3. Taggen Sie die Images mit Ihrer privaten Registry-URL:

   docker tag gcr.io/config-management-release/admission-webhook:v1.22.2-rc.1 \
    ${PRIVATE_REGISTRY_URL}/admission-webhook:v1.22.2-rc.1
   docker tag gcr.io/config-management-release/gcenode-askpass-sidecar:v1.22.2-rc.1 \
    ${PRIVATE_REGISTRY_URL}/gcenode-askpass-sidecar:v1.22.2-rc.1
   docker tag gcr.io/config-management-release/git-sync:v4.4.2-gke.3__linux_amd64 \
    ${PRIVATE_REGISTRY_URL}/git-sync:v4.4.2-gke.3__linux_amd64
   docker tag gcr.io/config-management-release/helm-sync:v1.22.2-rc.1 \
    ${PRIVATE_REGISTRY_URL}/helm-sync:v1.22.2-rc.1
   docker tag gcr.io/config-management-release/hydration-controller:v1.22.2-rc.1 \
    ${PRIVATE_REGISTRY_URL}/hydration-controller:v1.22.2-rc.1
   docker tag gcr.io/config-management-release/oci-sync:v1.22.2-rc.1 \
    ${PRIVATE_REGISTRY_URL}/oci-sync:v1.22.2-rc.1
   docker tag gcr.io/config-management-release/otelcontribcol:v0.119.0-gke.2 \
    ${PRIVATE_REGISTRY_URL}/otelcontribcol:v0.119.0-gke.2
   docker tag gcr.io/config-management-release/reconciler-manager:v1.22.2-rc.1 \
    ${PRIVATE_REGISTRY_URL}/reconciler-manager:v1.22.2-rc.1
   docker tag gcr.io/config-management-release/reconciler:v1.22.2-rc.1 \
    ${PRIVATE_REGISTRY_URL}/reconciler:v1.22.2-rc.1
   docker tag gcr.io/config-management-release/resource-group-controller:v1.22.2-rc.1 \
    ${PRIVATE_REGISTRY_URL}/resource-group-controller:v1.22.2-rc.1
   

4. Übertragen Sie die getaggten Images in Ihre private Registry:

   docker push ${PRIVATE_REGISTRY_URL}/admission-webhook:v1.22.2-rc.1
   docker push ${PRIVATE_REGISTRY_URL}/gcenode-askpass-sidecar:v1.22.2-rc.1
   docker push ${PRIVATE_REGISTRY_URL}/git-sync:v4.4.2-gke.3__linux_amd64
   docker push ${PRIVATE_REGISTRY_URL}/helm-sync:v1.22.2-rc.1
   docker push ${PRIVATE_REGISTRY_URL}/hydration-controller:v1.22.2-rc.1
   docker push ${PRIVATE_REGISTRY_URL}/oci-sync:v1.22.2-rc.1
   docker push ${PRIVATE_REGISTRY_URL}/otelcontribcol:v0.119.0-gke.2
   docker push ${PRIVATE_REGISTRY_URL}/reconciler-manager:v1.22.2-rc.1
   docker push ${PRIVATE_REGISTRY_URL}/reconciler:v1.22.2-rc.1
   docker push ${PRIVATE_REGISTRY_URL}/resource-group-controller:v1.22.2-rc.1
   

Wenn Sie die getaggten Images aus Ihrer privaten Registry abrufen können, war der Vorgang erfolgreich.

1.22.1

Führen Sie die folgenden Schritte aus, um die Images zu einer privaten Registry hinzuzufügen:

1. Rufen Sie die Config Sync-Images ab:

   docker pull gcr.io/config-management-release/admission-webhook:v1.22.1-rc.2
   docker pull gcr.io/config-management-release/gcenode-askpass-sidecar:v1.22.1-rc.2
   docker pull gcr.io/config-management-release/git-sync:v4.4.2-gke.2__linux_amd64
   docker pull gcr.io/config-management-release/helm-sync:v1.22.1-rc.2
   docker pull gcr.io/config-management-release/hydration-controller:v1.22.1-rc.2
   docker pull gcr.io/config-management-release/oci-sync:v1.22.1-rc.2
   docker pull gcr.io/config-management-release/otelcontribcol:v0.119.0-gke.2
   docker pull gcr.io/config-management-release/reconciler-manager:v1.22.1-rc.2
   docker pull gcr.io/config-management-release/reconciler:v1.22.1-rc.2
   docker pull gcr.io/config-management-release/resource-group-controller:v1.22.1-rc.2
   

2. Erstellen Sie eine Variable für Ihre private Registry-URL:

   export PRIVATE_REGISTRY_URL=PRIVATE_REGISTRY_URL
   

   Ersetzen Sie PRIVATE_REGISTRY_URL durch Ihre private Registry-URL.
3. Taggen Sie die Images mit Ihrer privaten Registry-URL:

   docker tag gcr.io/config-management-release/admission-webhook:v1.22.1-rc.2 \
    ${PRIVATE_REGISTRY_URL}/admission-webhook:v1.22.1-rc.2
   docker tag gcr.io/config-management-release/gcenode-askpass-sidecar:v1.22.1-rc.2 \
    ${PRIVATE_REGISTRY_URL}/gcenode-askpass-sidecar:v1.22.1-rc.2
   docker tag gcr.io/config-management-release/git-sync:v4.4.2-gke.2__linux_amd64 \
    ${PRIVATE_REGISTRY_URL}/git-sync:v4.4.2-gke.2__linux_amd64
   docker tag gcr.io/config-management-release/helm-sync:v1.22.1-rc.2 \
    ${PRIVATE_REGISTRY_URL}/helm-sync:v1.22.1-rc.2
   docker tag gcr.io/config-management-release/hydration-controller:v1.22.1-rc.2 \
    ${PRIVATE_REGISTRY_URL}/hydration-controller:v1.22.1-rc.2
   docker tag gcr.io/config-management-release/oci-sync:v1.22.1-rc.2 \
    ${PRIVATE_REGISTRY_URL}/oci-sync:v1.22.1-rc.2
   docker tag gcr.io/config-management-release/otelcontribcol:v0.119.0-gke.2 \
    ${PRIVATE_REGISTRY_URL}/otelcontribcol:v0.119.0-gke.2
   docker tag gcr.io/config-management-release/reconciler-manager:v1.22.1-rc.2 \
    ${PRIVATE_REGISTRY_URL}/reconciler-manager:v1.22.1-rc.2
   docker tag gcr.io/config-management-release/reconciler:v1.22.1-rc.2 \
    ${PRIVATE_REGISTRY_URL}/reconciler:v1.22.1-rc.2
   docker tag gcr.io/config-management-release/resource-group-controller:v1.22.1-rc.2 \
    ${PRIVATE_REGISTRY_URL}/resource-group-controller:v1.22.1-rc.2
   

4. Übertragen Sie die getaggten Images in Ihre private Registry:

   docker push ${PRIVATE_REGISTRY_URL}/admission-webhook:v1.22.1-rc.2
   docker push ${PRIVATE_REGISTRY_URL}/gcenode-askpass-sidecar:v1.22.1-rc.2
   docker push ${PRIVATE_REGISTRY_URL}/git-sync:v4.4.2-gke.2__linux_amd64
   docker push ${PRIVATE_REGISTRY_URL}/helm-sync:v1.22.1-rc.2
   docker push ${PRIVATE_REGISTRY_URL}/hydration-controller:v1.22.1-rc.2
   docker push ${PRIVATE_REGISTRY_URL}/oci-sync:v1.22.1-rc.2
   docker push ${PRIVATE_REGISTRY_URL}/otelcontribcol:v0.119.0-gke.2
   docker push ${PRIVATE_REGISTRY_URL}/reconciler-manager:v1.22.1-rc.2
   docker push ${PRIVATE_REGISTRY_URL}/reconciler:v1.22.1-rc.2
   docker push ${PRIVATE_REGISTRY_URL}/resource-group-controller:v1.22.1-rc.2
   

Wenn Sie die getaggten Images aus Ihrer privaten Registry abrufen können, war der Vorgang erfolgreich.

1.22.0

Führen Sie die folgenden Schritte aus, um die Images zu einer privaten Registry hinzuzufügen:

1. Rufen Sie die Config Sync-Images ab:

   docker pull gcr.io/config-management-release/admission-webhook:v1.22.0-rc.1
   docker pull gcr.io/config-management-release/gcenode-askpass-sidecar:v1.22.0-rc.1
   docker pull gcr.io/config-management-release/git-sync:v4.4.2-gke.2__linux_amd64
   docker pull gcr.io/config-management-release/helm-sync:v1.22.0-rc.1
   docker pull gcr.io/config-management-release/hydration-controller:v1.22.0-rc.1
   docker pull gcr.io/config-management-release/oci-sync:v1.22.0-rc.1
   docker pull gcr.io/config-management-release/otelcontribcol:v0.118.0-gke.10
   docker pull gcr.io/config-management-release/reconciler-manager:v1.22.0-rc.1
   docker pull gcr.io/config-management-release/reconciler:v1.22.0-rc.1
   docker pull gcr.io/config-management-release/resource-group-controller:v1.22.0-rc.1
   

2. Erstellen Sie eine Variable für Ihre private Registry-URL:

   export PRIVATE_REGISTRY_URL=PRIVATE_REGISTRY_URL
   

   Ersetzen Sie PRIVATE_REGISTRY_URL durch Ihre private Registry-URL.
3. Taggen Sie die Images mit Ihrer privaten Registry-URL:

   docker tag gcr.io/config-management-release/admission-webhook:v1.22.0-rc.1 \
    ${PRIVATE_REGISTRY_URL}/admission-webhook:v1.22.0-rc.1
   docker tag gcr.io/config-management-release/gcenode-askpass-sidecar:v1.22.0-rc.1 \
    ${PRIVATE_REGISTRY_URL}/gcenode-askpass-sidecar:v1.22.0-rc.1
   docker tag gcr.io/config-management-release/git-sync:v4.4.2-gke.2__linux_amd64 \
    ${PRIVATE_REGISTRY_URL}/git-sync:v4.4.2-gke.2__linux_amd64
   docker tag gcr.io/config-management-release/helm-sync:v1.22.0-rc.1 \
    ${PRIVATE_REGISTRY_URL}/helm-sync:v1.22.0-rc.1
   docker tag gcr.io/config-management-release/hydration-controller:v1.22.0-rc.1 \
    ${PRIVATE_REGISTRY_URL}/hydration-controller:v1.22.0-rc.1
   docker tag gcr.io/config-management-release/oci-sync:v1.22.0-rc.1 \
    ${PRIVATE_REGISTRY_URL}/oci-sync:v1.22.0-rc.1
   docker tag gcr.io/config-management-release/otelcontribcol:v0.118.0-gke.10 \
    ${PRIVATE_REGISTRY_URL}/otelcontribcol:v0.118.0-gke.10
   docker tag gcr.io/config-management-release/reconciler-manager:v1.22.0-rc.1 \
    ${PRIVATE_REGISTRY_URL}/reconciler-manager:v1.22.0-rc.1
   docker tag gcr.io/config-management-release/reconciler:v1.22.0-rc.1 \
    ${PRIVATE_REGISTRY_URL}/reconciler:v1.22.0-rc.1
   docker tag gcr.io/config-management-release/resource-group-controller:v1.22.0-rc.1 \
    ${PRIVATE_REGISTRY_URL}/resource-group-controller:v1.22.0-rc.1
   

4. Übertragen Sie die getaggten Images in Ihre private Registry:

   docker push ${PRIVATE_REGISTRY_URL}/admission-webhook:v1.22.0-rc.1
   docker push ${PRIVATE_REGISTRY_URL}/gcenode-askpass-sidecar:v1.22.0-rc.1
   docker push ${PRIVATE_REGISTRY_URL}/git-sync:v4.4.2-gke.2__linux_amd64
   docker push ${PRIVATE_REGISTRY_URL}/helm-sync:v1.22.0-rc.1
   docker push ${PRIVATE_REGISTRY_URL}/hydration-controller:v1.22.0-rc.1
   docker push ${PRIVATE_REGISTRY_URL}/oci-sync:v1.22.0-rc.1
   docker push ${PRIVATE_REGISTRY_URL}/otelcontribcol:v0.118.0-gke.10
   docker push ${PRIVATE_REGISTRY_URL}/reconciler-manager:v1.22.0-rc.1
   docker push ${PRIVATE_REGISTRY_URL}/reconciler:v1.22.0-rc.1
   docker push ${PRIVATE_REGISTRY_URL}/resource-group-controller:v1.22.0-rc.1
   

Wenn Sie die getaggten Images aus Ihrer privaten Registry abrufen können, war der Vorgang erfolgreich.

1.21.3

Führen Sie die folgenden Schritte aus, um die Images zu einer privaten Registry hinzuzufügen:

1. Rufen Sie die Config Sync-Images ab:

   docker pull gcr.io/config-management-release/admission-webhook:v1.21.3-rc.2
   docker pull gcr.io/config-management-release/gcenode-askpass-sidecar:v1.21.3-rc.2
   docker pull gcr.io/config-management-release/git-sync:v4.4.2-gke.1__linux_amd64
   docker pull gcr.io/config-management-release/helm-sync:v1.21.3-rc.2
   docker pull gcr.io/config-management-release/hydration-controller:v1.21.3-rc.2
   docker pull gcr.io/config-management-release/oci-sync:v1.21.3-rc.2
   docker pull gcr.io/config-management-release/otelcontribcol:v0.118.0-gke.10
   docker pull gcr.io/config-management-release/reconciler-manager:v1.21.3-rc.2
   docker pull gcr.io/config-management-release/reconciler:v1.21.3-rc.2
   docker pull gcr.io/config-management-release/resource-group-controller:v1.21.3-rc.2
   

2. Erstellen Sie eine Variable für Ihre private Registry-URL:

   export PRIVATE_REGISTRY_URL=PRIVATE_REGISTRY_URL
   

   Ersetzen Sie PRIVATE_REGISTRY_URL durch Ihre private Registry-URL.
3. Taggen Sie die Images mit Ihrer privaten Registry-URL:

   docker tag gcr.io/config-management-release/admission-webhook:v1.21.3-rc.2 \
    ${PRIVATE_REGISTRY_URL}/admission-webhook:v1.21.3-rc.2
   docker tag gcr.io/config-management-release/gcenode-askpass-sidecar:v1.21.3-rc.2 \
    ${PRIVATE_REGISTRY_URL}/gcenode-askpass-sidecar:v1.21.3-rc.2
   docker tag gcr.io/config-management-release/git-sync:v4.4.2-gke.1__linux_amd64 \
    ${PRIVATE_REGISTRY_URL}/git-sync:v4.4.2-gke.1__linux_amd64
   docker tag gcr.io/config-management-release/helm-sync:v1.21.3-rc.2 \
    ${PRIVATE_REGISTRY_URL}/helm-sync:v1.21.3-rc.2
   docker tag gcr.io/config-management-release/hydration-controller:v1.21.3-rc.2 \
    ${PRIVATE_REGISTRY_URL}/hydration-controller:v1.21.3-rc.2
   docker tag gcr.io/config-management-release/oci-sync:v1.21.3-rc.2 \
    ${PRIVATE_REGISTRY_URL}/oci-sync:v1.21.3-rc.2
   docker tag gcr.io/config-management-release/otelcontribcol:v0.118.0-gke.10 \
    ${PRIVATE_REGISTRY_URL}/otelcontribcol:v0.118.0-gke.10
   docker tag gcr.io/config-management-release/reconciler-manager:v1.21.3-rc.2 \
    ${PRIVATE_REGISTRY_URL}/reconciler-manager:v1.21.3-rc.2
   docker tag gcr.io/config-management-release/reconciler:v1.21.3-rc.2 \
    ${PRIVATE_REGISTRY_URL}/reconciler:v1.21.3-rc.2
   docker tag gcr.io/config-management-release/resource-group-controller:v1.21.3-rc.2 \
    ${PRIVATE_REGISTRY_URL}/resource-group-controller:v1.21.3-rc.2
   

4. Übertragen Sie die getaggten Images in Ihre private Registry:

   docker push ${PRIVATE_REGISTRY_URL}/admission-webhook:v1.21.3-rc.2
   docker push ${PRIVATE_REGISTRY_URL}/gcenode-askpass-sidecar:v1.21.3-rc.2
   docker push ${PRIVATE_REGISTRY_URL}/git-sync:v4.4.2-gke.1__linux_amd64
   docker push ${PRIVATE_REGISTRY_URL}/helm-sync:v1.21.3-rc.2
   docker push ${PRIVATE_REGISTRY_URL}/hydration-controller:v1.21.3-rc.2
   docker push ${PRIVATE_REGISTRY_URL}/oci-sync:v1.21.3-rc.2
   docker push ${PRIVATE_REGISTRY_URL}/otelcontribcol:v0.118.0-gke.10
   docker push ${PRIVATE_REGISTRY_URL}/reconciler-manager:v1.21.3-rc.2
   docker push ${PRIVATE_REGISTRY_URL}/reconciler:v1.21.3-rc.2
   docker push ${PRIVATE_REGISTRY_URL}/resource-group-controller:v1.21.3-rc.2
   

Wenn Sie die getaggten Images aus Ihrer privaten Registry abrufen können, war der Vorgang erfolgreich.

1.21.2

Führen Sie die folgenden Schritte aus, um die Images zu einer privaten Registry hinzuzufügen:

1. Rufen Sie die Config Sync-Images ab:

   docker pull gcr.io/config-management-release/admission-webhook:v1.21.2-rc.2
   docker pull gcr.io/config-management-release/gcenode-askpass-sidecar:v1.21.2-rc.2
   docker pull gcr.io/config-management-release/git-sync:v4.3.0-gke.19__linux_amd64
   docker pull gcr.io/config-management-release/helm-sync:v1.21.2-rc.2
   docker pull gcr.io/config-management-release/hydration-controller:v1.21.2-rc.2
   docker pull gcr.io/config-management-release/oci-sync:v1.21.2-rc.2
   docker pull gcr.io/config-management-release/otelcontribcol:v0.118.0-gke.9
   docker pull gcr.io/config-management-release/reconciler-manager:v1.21.2-rc.2
   docker pull gcr.io/config-management-release/reconciler:v1.21.2-rc.2
   docker pull gcr.io/config-management-release/resource-group-controller:v1.21.2-rc.2
   

2. Erstellen Sie eine Variable für Ihre private Registry-URL:

   export PRIVATE_REGISTRY_URL=PRIVATE_REGISTRY_URL
   

   Ersetzen Sie PRIVATE_REGISTRY_URL durch Ihre private Registry-URL.
3. Taggen Sie die Images mit Ihrer privaten Registry-URL:

   docker tag gcr.io/config-management-release/admission-webhook:v1.21.2-rc.2 \
    ${PRIVATE_REGISTRY_URL}/admission-webhook:v1.21.2-rc.2
   docker tag gcr.io/config-management-release/gcenode-askpass-sidecar:v1.21.2-rc.2 \
    ${PRIVATE_REGISTRY_URL}/gcenode-askpass-sidecar:v1.21.2-rc.2
   docker tag gcr.io/config-management-release/git-sync:v4.3.0-gke.19__linux_amd64 \
    ${PRIVATE_REGISTRY_URL}/git-sync:v4.3.0-gke.19__linux_amd64
   docker tag gcr.io/config-management-release/helm-sync:v1.21.2-rc.2 \
    ${PRIVATE_REGISTRY_URL}/helm-sync:v1.21.2-rc.2
   docker tag gcr.io/config-management-release/hydration-controller:v1.21.2-rc.2 \
    ${PRIVATE_REGISTRY_URL}/hydration-controller:v1.21.2-rc.2
   docker tag gcr.io/config-management-release/oci-sync:v1.21.2-rc.2 \
    ${PRIVATE_REGISTRY_URL}/oci-sync:v1.21.2-rc.2
   docker tag gcr.io/config-management-release/otelcontribcol:v0.118.0-gke.9 \
    ${PRIVATE_REGISTRY_URL}/otelcontribcol:v0.118.0-gke.9
   docker tag gcr.io/config-management-release/reconciler-manager:v1.21.2-rc.2 \
    ${PRIVATE_REGISTRY_URL}/reconciler-manager:v1.21.2-rc.2
   docker tag gcr.io/config-management-release/reconciler:v1.21.2-rc.2 \
    ${PRIVATE_REGISTRY_URL}/reconciler:v1.21.2-rc.2
   docker tag gcr.io/config-management-release/resource-group-controller:v1.21.2-rc.2 \
    ${PRIVATE_REGISTRY_URL}/resource-group-controller:v1.21.2-rc.2
   

4. Übertragen Sie die getaggten Images in Ihre private Registry:

   docker push ${PRIVATE_REGISTRY_URL}/admission-webhook:v1.21.2-rc.2
   docker push ${PRIVATE_REGISTRY_URL}/gcenode-askpass-sidecar:v1.21.2-rc.2
   docker push ${PRIVATE_REGISTRY_URL}/git-sync:v4.3.0-gke.19__linux_amd64
   docker push ${PRIVATE_REGISTRY_URL}/helm-sync:v1.21.2-rc.2
   docker push ${PRIVATE_REGISTRY_URL}/hydration-controller:v1.21.2-rc.2
   docker push ${PRIVATE_REGISTRY_URL}/oci-sync:v1.21.2-rc.2
   docker push ${PRIVATE_REGISTRY_URL}/otelcontribcol:v0.118.0-gke.9
   docker push ${PRIVATE_REGISTRY_URL}/reconciler-manager:v1.21.2-rc.2
   docker push ${PRIVATE_REGISTRY_URL}/reconciler:v1.21.2-rc.2
   docker push ${PRIVATE_REGISTRY_URL}/resource-group-controller:v1.21.2-rc.2
   

Wenn Sie die getaggten Images aus Ihrer privaten Registry abrufen können, war der Vorgang erfolgreich.

1.21.1

Führen Sie die folgenden Schritte aus, um die Images zu einer privaten Registry hinzuzufügen:

1. Rufen Sie die Config Sync-Images ab:

   docker pull gcr.io/config-management-release/admission-webhook:v1.21.1-rc.1
   docker pull gcr.io/config-management-release/gcenode-askpass-sidecar:v1.21.1-rc.1
   docker pull gcr.io/config-management-release/git-sync:v4.3.0-gke.16__linux_amd64
   docker pull gcr.io/config-management-release/helm-sync:v1.21.1-rc.1
   docker pull gcr.io/config-management-release/hydration-controller:v1.21.1-rc.1
   docker pull gcr.io/config-management-release/oci-sync:v1.21.1-rc.1
   docker pull gcr.io/config-management-release/otelcontribcol:v0.118.0-gke.9
   docker pull gcr.io/config-management-release/reconciler-manager:v1.21.1-rc.1
   docker pull gcr.io/config-management-release/reconciler:v1.21.1-rc.1
   docker pull gcr.io/config-management-release/resource-group-controller:v1.21.1-rc.1
   

2. Erstellen Sie eine Variable für Ihre private Registry-URL:

   export PRIVATE_REGISTRY_URL=PRIVATE_REGISTRY_URL
   

   Ersetzen Sie PRIVATE_REGISTRY_URL durch Ihre private Registry-URL.
3. Taggen Sie die Images mit Ihrer privaten Registry-URL:

   docker tag gcr.io/config-management-release/admission-webhook:v1.21.1-rc.1 \
    ${PRIVATE_REGISTRY_URL}/admission-webhook:v1.21.1-rc.1
   docker tag gcr.io/config-management-release/gcenode-askpass-sidecar:v1.21.1-rc.1 \
    ${PRIVATE_REGISTRY_URL}/gcenode-askpass-sidecar:v1.21.1-rc.1
   docker tag gcr.io/config-management-release/git-sync:v4.3.0-gke.16__linux_amd64 \
    ${PRIVATE_REGISTRY_URL}/git-sync:v4.3.0-gke.16__linux_amd64
   docker tag gcr.io/config-management-release/helm-sync:v1.21.1-rc.1 \
    ${PRIVATE_REGISTRY_URL}/helm-sync:v1.21.1-rc.1
   docker tag gcr.io/config-management-release/hydration-controller:v1.21.1-rc.1 \
    ${PRIVATE_REGISTRY_URL}/hydration-controller:v1.21.1-rc.1
   docker tag gcr.io/config-management-release/oci-sync:v1.21.1-rc.1 \
    ${PRIVATE_REGISTRY_URL}/oci-sync:v1.21.1-rc.1
   docker tag gcr.io/config-management-release/otelcontribcol:v0.118.0-gke.9 \
    ${PRIVATE_REGISTRY_URL}/otelcontribcol:v0.118.0-gke.9
   docker tag gcr.io/config-management-release/reconciler-manager:v1.21.1-rc.1 \
    ${PRIVATE_REGISTRY_URL}/reconciler-manager:v1.21.1-rc.1
   docker tag gcr.io/config-management-release/reconciler:v1.21.1-rc.1 \
    ${PRIVATE_REGISTRY_URL}/reconciler:v1.21.1-rc.1
   docker tag gcr.io/config-management-release/resource-group-controller:v1.21.1-rc.1 \
    ${PRIVATE_REGISTRY_URL}/resource-group-controller:v1.21.1-rc.1
   

4. Übertragen Sie die getaggten Images in Ihre private Registry:

   docker push ${PRIVATE_REGISTRY_URL}/admission-webhook:v1.21.1-rc.1
   docker push ${PRIVATE_REGISTRY_URL}/gcenode-askpass-sidecar:v1.21.1-rc.1
   docker push ${PRIVATE_REGISTRY_URL}/git-sync:v4.3.0-gke.16__linux_amd64
   docker push ${PRIVATE_REGISTRY_URL}/helm-sync:v1.21.1-rc.1
   docker push ${PRIVATE_REGISTRY_URL}/hydration-controller:v1.21.1-rc.1
   docker push ${PRIVATE_REGISTRY_URL}/oci-sync:v1.21.1-rc.1
   docker push ${PRIVATE_REGISTRY_URL}/otelcontribcol:v0.118.0-gke.9
   docker push ${PRIVATE_REGISTRY_URL}/reconciler-manager:v1.21.1-rc.1
   docker push ${PRIVATE_REGISTRY_URL}/reconciler:v1.21.1-rc.1
   docker push ${PRIVATE_REGISTRY_URL}/resource-group-controller:v1.21.1-rc.1
   

Wenn Sie die getaggten Images aus Ihrer privaten Registry abrufen können, war der Vorgang erfolgreich.

1.21.0

Führen Sie die folgenden Schritte aus, um die Images zu einer privaten Registry hinzuzufügen:

1. Rufen Sie die Config Sync-Images ab:

   docker pull gcr.io/config-management-release/admission-webhook:v1.21.0-rc.2
   docker pull gcr.io/config-management-release/gcenode-askpass-sidecar:v1.21.0-rc.2
   docker pull gcr.io/config-management-release/git-sync:v4.3.0-gke.16__linux_amd64
   docker pull gcr.io/config-management-release/helm-sync:v1.21.0-rc.2
   docker pull gcr.io/config-management-release/hydration-controller:v1.21.0-rc.2
   docker pull gcr.io/config-management-release/oci-sync:v1.21.0-rc.2
   docker pull gcr.io/config-management-release/otelcontribcol:v0.118.0-gke.7
   docker pull gcr.io/config-management-release/reconciler-manager:v1.21.0-rc.2
   docker pull gcr.io/config-management-release/reconciler:v1.21.0-rc.2
   docker pull gcr.io/config-management-release/resource-group-controller:v1.21.0-rc.2
   

2. Erstellen Sie eine Variable für Ihre private Registry-URL:

   export PRIVATE_REGISTRY_URL=PRIVATE_REGISTRY_URL
   

   Ersetzen Sie PRIVATE_REGISTRY_URL durch Ihre private Registry-URL.
3. Taggen Sie die Images mit Ihrer privaten Registry-URL:

   docker tag gcr.io/config-management-release/admission-webhook:v1.21.0-rc.2 \
    ${PRIVATE_REGISTRY_URL}/admission-webhook:v1.21.0-rc.2
   docker tag gcr.io/config-management-release/gcenode-askpass-sidecar:v1.21.0-rc.2 \
    ${PRIVATE_REGISTRY_URL}/gcenode-askpass-sidecar:v1.21.0-rc.2
   docker tag gcr.io/config-management-release/git-sync:v4.3.0-gke.16__linux_amd64 \
    ${PRIVATE_REGISTRY_URL}/git-sync:v4.3.0-gke.16__linux_amd64
   docker tag gcr.io/config-management-release/helm-sync:v1.21.0-rc.2 \
    ${PRIVATE_REGISTRY_URL}/helm-sync:v1.21.0-rc.2
   docker tag gcr.io/config-management-release/hydration-controller:v1.21.0-rc.2 \
    ${PRIVATE_REGISTRY_URL}/hydration-controller:v1.21.0-rc.2
   docker tag gcr.io/config-management-release/oci-sync:v1.21.0-rc.2 \
    ${PRIVATE_REGISTRY_URL}/oci-sync:v1.21.0-rc.2
   docker tag gcr.io/config-management-release/otelcontribcol:v0.118.0-gke.7 \
    ${PRIVATE_REGISTRY_URL}/otelcontribcol:v0.118.0-gke.7
   docker tag gcr.io/config-management-release/reconciler-manager:v1.21.0-rc.2 \
    ${PRIVATE_REGISTRY_URL}/reconciler-manager:v1.21.0-rc.2
   docker tag gcr.io/config-management-release/reconciler:v1.21.0-rc.2 \
    ${PRIVATE_REGISTRY_URL}/reconciler:v1.21.0-rc.2
   docker tag gcr.io/config-management-release/resource-group-controller:v1.21.0-rc.2 \
    ${PRIVATE_REGISTRY_URL}/resource-group-controller:v1.21.0-rc.2
   

4. Übertragen Sie die getaggten Images in Ihre private Registry:

   docker push ${PRIVATE_REGISTRY_URL}/admission-webhook:v1.21.0-rc.2
   docker push ${PRIVATE_REGISTRY_URL}/gcenode-askpass-sidecar:v1.21.0-rc.2
   docker push ${PRIVATE_REGISTRY_URL}/git-sync:v4.3.0-gke.16__linux_amd64
   docker push ${PRIVATE_REGISTRY_URL}/helm-sync:v1.21.0-rc.2
   docker push ${PRIVATE_REGISTRY_URL}/hydration-controller:v1.21.0-rc.2
   docker push ${PRIVATE_REGISTRY_URL}/oci-sync:v1.21.0-rc.2
   docker push ${PRIVATE_REGISTRY_URL}/otelcontribcol:v0.118.0-gke.7
   docker push ${PRIVATE_REGISTRY_URL}/reconciler-manager:v1.21.0-rc.2
   docker push ${PRIVATE_REGISTRY_URL}/reconciler:v1.21.0-rc.2
   docker push ${PRIVATE_REGISTRY_URL}/resource-group-controller:v1.21.0-rc.2
   

Wenn Sie die getaggten Images aus Ihrer privaten Registry abrufen können, war der Vorgang erfolgreich.

1.20.3

Führen Sie die folgenden Schritte aus, um die Images zu einer privaten Registry hinzuzufügen:

1. Rufen Sie die Config Sync-Images ab:

   docker pull gcr.io/config-management-release/admission-webhook:v1.20.3-rc.1
   docker pull gcr.io/config-management-release/gcenode-askpass-sidecar:v1.20.3-rc.1
   docker pull gcr.io/config-management-release/git-sync:v4.3.0-gke.11__linux_amd64
   docker pull gcr.io/config-management-release/helm-sync:v1.20.3-rc.1
   docker pull gcr.io/config-management-release/hydration-controller:v1.20.3-rc.1
   docker pull gcr.io/config-management-release/oci-sync:v1.20.3-rc.1
   docker pull gcr.io/config-management-release/otelcontribcol:v0.103.0-gke.8
   docker pull gcr.io/config-management-release/reconciler-manager:v1.20.3-rc.1
   docker pull gcr.io/config-management-release/reconciler:v1.20.3-rc.1
   docker pull gcr.io/config-management-release/resource-group-controller:v1.20.3-rc.1
   

2. Erstellen Sie eine Variable für Ihre private Registry-URL:

   export PRIVATE_REGISTRY_URL=PRIVATE_REGISTRY_URL
   

   Ersetzen Sie PRIVATE_REGISTRY_URL durch Ihre private Registry-URL.
3. Taggen Sie die Images mit Ihrer privaten Registry-URL:

   docker tag gcr.io/config-management-release/admission-webhook:v1.20.3-rc.1 \
    ${PRIVATE_REGISTRY_URL}/admission-webhook:v1.20.3-rc.1
   docker tag gcr.io/config-management-release/gcenode-askpass-sidecar:v1.20.3-rc.1 \
    ${PRIVATE_REGISTRY_URL}/gcenode-askpass-sidecar:v1.20.3-rc.1
   docker tag gcr.io/config-management-release/git-sync:v4.3.0-gke.11__linux_amd64 \
    ${PRIVATE_REGISTRY_URL}/git-sync:v4.3.0-gke.11__linux_amd64
   docker tag gcr.io/config-management-release/helm-sync:v1.20.3-rc.1 \
    ${PRIVATE_REGISTRY_URL}/helm-sync:v1.20.3-rc.1
   docker tag gcr.io/config-management-release/hydration-controller:v1.20.3-rc.1 \
    ${PRIVATE_REGISTRY_URL}/hydration-controller:v1.20.3-rc.1
   docker tag gcr.io/config-management-release/oci-sync:v1.20.3-rc.1 \
    ${PRIVATE_REGISTRY_URL}/oci-sync:v1.20.3-rc.1
   docker tag gcr.io/config-management-release/otelcontribcol:v0.103.0-gke.8 \
    ${PRIVATE_REGISTRY_URL}/otelcontribcol:v0.103.0-gke.8
   docker tag gcr.io/config-management-release/reconciler-manager:v1.20.3-rc.1 \
    ${PRIVATE_REGISTRY_URL}/reconciler-manager:v1.20.3-rc.1
   docker tag gcr.io/config-management-release/reconciler:v1.20.3-rc.1 \
    ${PRIVATE_REGISTRY_URL}/reconciler:v1.20.3-rc.1
   docker tag gcr.io/config-management-release/resource-group-controller:v1.20.3-rc.1 \
    ${PRIVATE_REGISTRY_URL}/resource-group-controller:v1.20.3-rc.1
   

4. Übertragen Sie die getaggten Images in Ihre private Registry:

   docker push ${PRIVATE_REGISTRY_URL}/admission-webhook:v1.20.3-rc.1
   docker push ${PRIVATE_REGISTRY_URL}/gcenode-askpass-sidecar:v1.20.3-rc.1
   docker push ${PRIVATE_REGISTRY_URL}/git-sync:v4.3.0-gke.11__linux_amd64
   docker push ${PRIVATE_REGISTRY_URL}/helm-sync:v1.20.3-rc.1
   docker push ${PRIVATE_REGISTRY_URL}/hydration-controller:v1.20.3-rc.1
   docker push ${PRIVATE_REGISTRY_URL}/oci-sync:v1.20.3-rc.1
   docker push ${PRIVATE_REGISTRY_URL}/otelcontribcol:v0.103.0-gke.8
   docker push ${PRIVATE_REGISTRY_URL}/reconciler-manager:v1.20.3-rc.1
   docker push ${PRIVATE_REGISTRY_URL}/reconciler:v1.20.3-rc.1
   docker push ${PRIVATE_REGISTRY_URL}/resource-group-controller:v1.20.3-rc.1
   

Wenn Sie die getaggten Images aus Ihrer privaten Registry abrufen können, war der Vorgang erfolgreich.

1.20.2

Führen Sie die folgenden Schritte aus, um die Images zu einer privaten Registry hinzuzufügen:

1. Rufen Sie die Config Sync-Images ab:

   docker pull gcr.io/config-management-release/admission-webhook:v1.20.2-rc.2
   docker pull gcr.io/config-management-release/gcenode-askpass-sidecar:v1.20.2-rc.2
   docker pull gcr.io/config-management-release/git-sync:v4.3.0-gke.9__linux_amd64
   docker pull gcr.io/config-management-release/helm-sync:v1.20.2-rc.2
   docker pull gcr.io/config-management-release/hydration-controller:v1.20.2-rc.2
   docker pull gcr.io/config-management-release/oci-sync:v1.20.2-rc.2
   docker pull gcr.io/config-management-release/otelcontribcol:v0.103.0-gke.7
   docker pull gcr.io/config-management-release/reconciler-manager:v1.20.2-rc.2
   docker pull gcr.io/config-management-release/reconciler:v1.20.2-rc.2
   docker pull gcr.io/config-management-release/resource-group-controller:v1.20.2-rc.2
   

2. Erstellen Sie eine Variable für Ihre private Registry-URL:

   export PRIVATE_REGISTRY_URL=PRIVATE_REGISTRY_URL
   

   Ersetzen Sie PRIVATE_REGISTRY_URL durch Ihre private Registry-URL.
3. Taggen Sie die Images mit Ihrer privaten Registry-URL:

   docker tag gcr.io/config-management-release/admission-webhook:v1.20.2-rc.2 \
    ${PRIVATE_REGISTRY_URL}/admission-webhook:v1.20.2-rc.2
   docker tag gcr.io/config-management-release/gcenode-askpass-sidecar:v1.20.2-rc.2 \
    ${PRIVATE_REGISTRY_URL}/gcenode-askpass-sidecar:v1.20.2-rc.2
   docker tag gcr.io/config-management-release/git-sync:v4.3.0-gke.9__linux_amd64 \
    ${PRIVATE_REGISTRY_URL}/git-sync:v4.3.0-gke.9__linux_amd64
   docker tag gcr.io/config-management-release/helm-sync:v1.20.2-rc.2 \
    ${PRIVATE_REGISTRY_URL}/helm-sync:v1.20.2-rc.2
   docker tag gcr.io/config-management-release/hydration-controller:v1.20.2-rc.2 \
    ${PRIVATE_REGISTRY_URL}/hydration-controller:v1.20.2-rc.2
   docker tag gcr.io/config-management-release/oci-sync:v1.20.2-rc.2 \
    ${PRIVATE_REGISTRY_URL}/oci-sync:v1.20.2-rc.2
   docker tag gcr.io/config-management-release/otelcontribcol:v0.103.0-gke.7 \
    ${PRIVATE_REGISTRY_URL}/otelcontribcol:v0.103.0-gke.7
   docker tag gcr.io/config-management-release/reconciler-manager:v1.20.2-rc.2 \
    ${PRIVATE_REGISTRY_URL}/reconciler-manager:v1.20.2-rc.2
   docker tag gcr.io/config-management-release/reconciler:v1.20.2-rc.2 \
    ${PRIVATE_REGISTRY_URL}/reconciler:v1.20.2-rc.2
   docker tag gcr.io/config-management-release/resource-group-controller:v1.20.2-rc.2 \
    ${PRIVATE_REGISTRY_URL}/resource-group-controller:v1.20.2-rc.2
   

4. Übertragen Sie die getaggten Images in Ihre private Registry:

   docker push ${PRIVATE_REGISTRY_URL}/admission-webhook:v1.20.2-rc.2
   docker push ${PRIVATE_REGISTRY_URL}/gcenode-askpass-sidecar:v1.20.2-rc.2
   docker push ${PRIVATE_REGISTRY_URL}/git-sync:v4.3.0-gke.9__linux_amd64
   docker push ${PRIVATE_REGISTRY_URL}/helm-sync:v1.20.2-rc.2
   docker push ${PRIVATE_REGISTRY_URL}/hydration-controller:v1.20.2-rc.2
   docker push ${PRIVATE_REGISTRY_URL}/oci-sync:v1.20.2-rc.2
   docker push ${PRIVATE_REGISTRY_URL}/otelcontribcol:v0.103.0-gke.7
   docker push ${PRIVATE_REGISTRY_URL}/reconciler-manager:v1.20.2-rc.2
   docker push ${PRIVATE_REGISTRY_URL}/reconciler:v1.20.2-rc.2
   docker push ${PRIVATE_REGISTRY_URL}/resource-group-controller:v1.20.2-rc.2
   

Wenn Sie die getaggten Images aus Ihrer privaten Registry abrufen können, war der Vorgang erfolgreich.

1.20.1

Führen Sie die folgenden Schritte aus, um die Images zu einer privaten Registry hinzuzufügen:

1. Rufen Sie die Config Sync-Images ab:

   docker pull gcr.io/config-management-release/admission-webhook:v1.20.1-rc.1
   docker pull gcr.io/config-management-release/gcenode-askpass-sidecar:v1.20.1-rc.1
   docker pull gcr.io/config-management-release/git-sync:v4.3.0-gke.4__linux_amd64
   docker pull gcr.io/config-management-release/helm-sync:v1.20.1-rc.1
   docker pull gcr.io/config-management-release/hydration-controller:v1.20.1-rc.1
   docker pull gcr.io/config-management-release/oci-sync:v1.20.1-rc.1
   docker pull gcr.io/config-management-release/otelcontribcol:v0.103.0-gke.7
   docker pull gcr.io/config-management-release/reconciler-manager:v1.20.1-rc.1
   docker pull gcr.io/config-management-release/reconciler:v1.20.1-rc.1
   docker pull gcr.io/config-management-release/resource-group-controller:v1.20.1-rc.1
   

2. Erstellen Sie eine Variable für Ihre private Registry-URL:

   export PRIVATE_REGISTRY_URL=PRIVATE_REGISTRY_URL
   

   Ersetzen Sie PRIVATE_REGISTRY_URL durch Ihre private Registry-URL.
3. Taggen Sie die Images mit Ihrer privaten Registry-URL:

   docker tag gcr.io/config-management-release/admission-webhook:v1.20.1-rc.1 \
    ${PRIVATE_REGISTRY_URL}/admission-webhook:v1.20.1-rc.1
   docker tag gcr.io/config-management-release/gcenode-askpass-sidecar:v1.20.1-rc.1 \
    ${PRIVATE_REGISTRY_URL}/gcenode-askpass-sidecar:v1.20.1-rc.1
   docker tag gcr.io/config-management-release/git-sync:v4.3.0-gke.4__linux_amd64 \
    ${PRIVATE_REGISTRY_URL}/git-sync:v4.3.0-gke.4__linux_amd64
   docker tag gcr.io/config-management-release/helm-sync:v1.20.1-rc.1 \
    ${PRIVATE_REGISTRY_URL}/helm-sync:v1.20.1-rc.1
   docker tag gcr.io/config-management-release/hydration-controller:v1.20.1-rc.1 \
    ${PRIVATE_REGISTRY_URL}/hydration-controller:v1.20.1-rc.1
   docker tag gcr.io/config-management-release/oci-sync:v1.20.1-rc.1 \
    ${PRIVATE_REGISTRY_URL}/oci-sync:v1.20.1-rc.1
   docker tag gcr.io/config-management-release/otelcontribcol:v0.103.0-gke.7 \
    ${PRIVATE_REGISTRY_URL}/otelcontribcol:v0.103.0-gke.7
   docker tag gcr.io/config-management-release/reconciler-manager:v1.20.1-rc.1 \
    ${PRIVATE_REGISTRY_URL}/reconciler-manager:v1.20.1-rc.1
   docker tag gcr.io/config-management-release/reconciler:v1.20.1-rc.1 \
    ${PRIVATE_REGISTRY_URL}/reconciler:v1.20.1-rc.1
   docker tag gcr.io/config-management-release/resource-group-controller:v1.20.1-rc.1 \
    ${PRIVATE_REGISTRY_URL}/resource-group-controller:v1.20.1-rc.1
   

4. Übertragen Sie die getaggten Images in Ihre private Registry:

   docker push ${PRIVATE_REGISTRY_URL}/admission-webhook:v1.20.1-rc.1
   docker push ${PRIVATE_REGISTRY_URL}/gcenode-askpass-sidecar:v1.20.1-rc.1
   docker push ${PRIVATE_REGISTRY_URL}/git-sync:v4.3.0-gke.4__linux_amd64
   docker push ${PRIVATE_REGISTRY_URL}/helm-sync:v1.20.1-rc.1
   docker push ${PRIVATE_REGISTRY_URL}/hydration-controller:v1.20.1-rc.1
   docker push ${PRIVATE_REGISTRY_URL}/oci-sync:v1.20.1-rc.1
   docker push ${PRIVATE_REGISTRY_URL}/otelcontribcol:v0.103.0-gke.7
   docker push ${PRIVATE_REGISTRY_URL}/reconciler-manager:v1.20.1-rc.1
   docker push ${PRIVATE_REGISTRY_URL}/reconciler:v1.20.1-rc.1
   docker push ${PRIVATE_REGISTRY_URL}/resource-group-controller:v1.20.1-rc.1
   

Wenn Sie die getaggten Images aus Ihrer privaten Registry abrufen können, war der Vorgang erfolgreich.

1.20.0

Führen Sie die folgenden Schritte aus, um die Images zu einer privaten Registry hinzuzufügen:

1. Rufen Sie die Config Sync-Images ab:

   docker pull gcr.io/config-management-release/admission-webhook:v1.20.0-rc.3
   docker pull gcr.io/config-management-release/gcenode-askpass-sidecar:v1.20.0-rc.3
   docker pull gcr.io/config-management-release/git-sync:v4.3.0-gke.2__linux_amd64
   docker pull gcr.io/config-management-release/helm-sync:v1.20.0-rc.3
   docker pull gcr.io/config-management-release/hydration-controller:v1.20.0-rc.3
   docker pull gcr.io/config-management-release/oci-sync:v1.20.0-rc.3
   docker pull gcr.io/config-management-release/otelcontribcol:v0.103.0-gke.5
   docker pull gcr.io/config-management-release/reconciler-manager:v1.20.0-rc.3
   docker pull gcr.io/config-management-release/reconciler:v1.20.0-rc.3
   docker pull gcr.io/config-management-release/resource-group-controller:v1.20.0-rc.3
   

2. Erstellen Sie eine Variable für Ihre private Registry-URL:

   export PRIVATE_REGISTRY_URL=PRIVATE_REGISTRY_URL
   

   Ersetzen Sie PRIVATE_REGISTRY_URL durch Ihre private Registry-URL.
3. Taggen Sie die Images mit Ihrer privaten Registry-URL:

   docker tag gcr.io/config-management-release/admission-webhook:v1.20.0-rc.3 \
    ${PRIVATE_REGISTRY_URL}/admission-webhook:v1.20.0-rc.3
   docker tag gcr.io/config-management-release/gcenode-askpass-sidecar:v1.20.0-rc.3 \
    ${PRIVATE_REGISTRY_URL}/gcenode-askpass-sidecar:v1.20.0-rc.3
   docker tag gcr.io/config-management-release/git-sync:v4.3.0-gke.2__linux_amd64 \
    ${PRIVATE_REGISTRY_URL}/git-sync:v4.3.0-gke.2__linux_amd64
   docker tag gcr.io/config-management-release/helm-sync:v1.20.0-rc.3 \
    ${PRIVATE_REGISTRY_URL}/helm-sync:v1.20.0-rc.3
   docker tag gcr.io/config-management-release/hydration-controller:v1.20.0-rc.3 \
    ${PRIVATE_REGISTRY_URL}/hydration-controller:v1.20.0-rc.3
   docker tag gcr.io/config-management-release/oci-sync:v1.20.0-rc.3 \
    ${PRIVATE_REGISTRY_URL}/oci-sync:v1.20.0-rc.3
   docker tag gcr.io/config-management-release/otelcontribcol:v0.103.0-gke.5 \
    ${PRIVATE_REGISTRY_URL}/otelcontribcol:v0.103.0-gke.5
   docker tag gcr.io/config-management-release/reconciler-manager:v1.20.0-rc.3 \
    ${PRIVATE_REGISTRY_URL}/reconciler-manager:v1.20.0-rc.3
   docker tag gcr.io/config-management-release/reconciler:v1.20.0-rc.3 \
    ${PRIVATE_REGISTRY_URL}/reconciler:v1.20.0-rc.3
   docker tag gcr.io/config-management-release/resource-group-controller:v1.20.0-rc.3 \
    ${PRIVATE_REGISTRY_URL}/resource-group-controller:v1.20.0-rc.3
   

4. Übertragen Sie die getaggten Images in Ihre private Registry:

   docker push ${PRIVATE_REGISTRY_URL}/admission-webhook:v1.20.0-rc.3
   docker push ${PRIVATE_REGISTRY_URL}/gcenode-askpass-sidecar:v1.20.0-rc.3
   docker push ${PRIVATE_REGISTRY_URL}/git-sync:v4.3.0-gke.2__linux_amd64
   docker push ${PRIVATE_REGISTRY_URL}/helm-sync:v1.20.0-rc.3
   docker push ${PRIVATE_REGISTRY_URL}/hydration-controller:v1.20.0-rc.3
   docker push ${PRIVATE_REGISTRY_URL}/oci-sync:v1.20.0-rc.3
   docker push ${PRIVATE_REGISTRY_URL}/otelcontribcol:v0.103.0-gke.5
   docker push ${PRIVATE_REGISTRY_URL}/reconciler-manager:v1.20.0-rc.3
   docker push ${PRIVATE_REGISTRY_URL}/reconciler:v1.20.0-rc.3
   docker push ${PRIVATE_REGISTRY_URL}/resource-group-controller:v1.20.0-rc.3
   

Wenn Sie die getaggten Images aus Ihrer privaten Registry abrufen können, war der Vorgang erfolgreich.