Aggiornamento di Config Sync utilizzando un registro privato

Ogni versione di Config Sync richiede un set specifico di immagini con versione per l'esecuzione. Se utilizzi un registry privato, devi eseguire il pull, il tagging e il push di queste immagini nel registry privato prima di poter installare i componenti di Config Sync o eseguire l'upgrade della versione di Config Sync.

Nota: un registry privato viene configurato nell'ambito del processo di configurazione del cluster di amministrazione di Google Distributed Cloud. Config Sync rileva automaticamente quando è stato configurato un registry privato e si assicura che venga utilizzato da Config Sync. Per saperne di più, consulta Crea un cluster di amministrazione nella documentazione di Google Distributed Cloud.

Aggiungi immagini a un registry privato

Per eseguire il push di immagini Config Sync specifiche per la versione in un registry privato, fai clic sull'icona con il segno più per la versione che vuoi utilizzare e completa i passaggi elencati.

Nota: utilizza un client da cui puoi eseguire il pull da gcr.io e il push nel tuo registry privato.

1.25.2

Per aggiungere le immagini a un registry privato, completa i seguenti passaggi:

1. Esegui il pull delle immagini di Config Sync:

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

2. Crea una variabile per l'URL del tuo registry privato:

   export PRIVATE_REGISTRY_URL=PRIVATE_REGISTRY_URL
   

   Sostituisci PRIVATE_REGISTRY_URL con l'URL del tuo registry privato.
3. Tagga le immagini con l'URL del tuo registro privato:

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

4. Esegui il push delle immagini taggate nel tuo registro privato:

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

Se riesci a eseguire il pull delle immagini taggate dal tuo registry privato, la procedura è andata a buon fine.

1.25.1

Per aggiungere le immagini a un registry privato, completa i seguenti passaggi:

1. Esegui il pull delle immagini di Config Sync:

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

2. Crea una variabile per l'URL del tuo registry privato:

   export PRIVATE_REGISTRY_URL=PRIVATE_REGISTRY_URL
   

   Sostituisci PRIVATE_REGISTRY_URL con l'URL del tuo registry privato.
3. Tagga le immagini con l'URL del tuo registro privato:

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

4. Esegui il push delle immagini taggate nel tuo registro privato:

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

Se riesci a eseguire il pull delle immagini taggate dal tuo registry privato, la procedura è andata a buon fine.

1.25.0

Per aggiungere le immagini a un registry privato, completa i seguenti passaggi:

1. Esegui il pull delle immagini di Config Sync:

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

2. Crea una variabile per l'URL del tuo registry privato:

   export PRIVATE_REGISTRY_URL=PRIVATE_REGISTRY_URL
   

   Sostituisci PRIVATE_REGISTRY_URL con l'URL del tuo registry privato.
3. Tagga le immagini con l'URL del tuo registro privato:

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

4. Esegui il push delle immagini taggate nel tuo registro privato:

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

Se riesci a eseguire il pull delle immagini taggate dal tuo registry privato, la procedura è andata a buon fine.

1.24.3

Per aggiungere le immagini a un registry privato, completa i seguenti passaggi:

1. Esegui il pull delle immagini di Config Sync:

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

2. Crea una variabile per l'URL del tuo registry privato:

   export PRIVATE_REGISTRY_URL=PRIVATE_REGISTRY_URL
   

   Sostituisci PRIVATE_REGISTRY_URL con l'URL del tuo registry privato.
3. Tagga le immagini con l'URL del tuo registro privato:

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

4. Esegui il push delle immagini taggate nel tuo registro privato:

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

Se riesci a eseguire il pull delle immagini taggate dal tuo registry privato, la procedura è andata a buon fine.

1.24.2

Per aggiungere le immagini a un registry privato, completa i seguenti passaggi:

1. Esegui il pull delle immagini di Config Sync:

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

2. Crea una variabile per l'URL del tuo registry privato:

   export PRIVATE_REGISTRY_URL=PRIVATE_REGISTRY_URL
   

   Sostituisci PRIVATE_REGISTRY_URL con l'URL del tuo registry privato.
3. Tagga le immagini con l'URL del tuo registro privato:

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

4. Esegui il push delle immagini taggate nel tuo registro privato:

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

Se riesci a eseguire il pull delle immagini taggate dal tuo registry privato, la procedura è andata a buon fine.

1.24.1

Per aggiungere le immagini a un registry privato, completa i seguenti passaggi:

1. Esegui il pull delle immagini di Config Sync:

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

2. Crea una variabile per l'URL del tuo registry privato:

   export PRIVATE_REGISTRY_URL=PRIVATE_REGISTRY_URL
   

   Sostituisci PRIVATE_REGISTRY_URL con l'URL del tuo registry privato.
3. Tagga le immagini con l'URL del tuo registro privato:

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

4. Esegui il push delle immagini taggate nel tuo registro privato:

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

Se riesci a eseguire il pull delle immagini taggate dal tuo registry privato, la procedura è andata a buon fine.

1.24.0

Per aggiungere le immagini a un registry privato, completa i seguenti passaggi:

1. Esegui il pull delle immagini di Config Sync:

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

2. Crea una variabile per l'URL del tuo registry privato:

   export PRIVATE_REGISTRY_URL=PRIVATE_REGISTRY_URL
   

   Sostituisci PRIVATE_REGISTRY_URL con l'URL del tuo registry privato.
3. Tagga le immagini con l'URL del tuo registro privato:

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

4. Esegui il push delle immagini taggate nel tuo registro privato:

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

Se riesci a eseguire il pull delle immagini taggate dal tuo registry privato, la procedura è andata a buon fine.

1.23.3

Per aggiungere le immagini a un registry privato, completa i seguenti passaggi:

1. Esegui il pull delle immagini di Config Sync:

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

2. Crea una variabile per l'URL del tuo registry privato:

   export PRIVATE_REGISTRY_URL=PRIVATE_REGISTRY_URL
   

   Sostituisci PRIVATE_REGISTRY_URL con l'URL del tuo registry privato.
3. Tagga le immagini con l'URL del tuo registro privato:

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

4. Esegui il push delle immagini taggate nel tuo registro privato:

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

Se riesci a eseguire il pull delle immagini taggate dal tuo registry privato, la procedura è andata a buon fine.

1.23.2

Per aggiungere le immagini a un registry privato, completa i seguenti passaggi:

1. Esegui il pull delle immagini di Config Sync:

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

2. Crea una variabile per l'URL del tuo registry privato:

   export PRIVATE_REGISTRY_URL=PRIVATE_REGISTRY_URL
   

   Sostituisci PRIVATE_REGISTRY_URL con l'URL del tuo registry privato.
3. Tagga le immagini con l'URL del tuo registro privato:

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

4. Esegui il push delle immagini taggate nel tuo registro privato:

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

Se riesci a eseguire il pull delle immagini taggate dal tuo registry privato, la procedura è andata a buon fine.

1.23.1

Per aggiungere le immagini a un registry privato, completa i seguenti passaggi:

1. Esegui il pull delle immagini di Config Sync:

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

2. Crea una variabile per l'URL del tuo registry privato:

   export PRIVATE_REGISTRY_URL=PRIVATE_REGISTRY_URL
   

   Sostituisci PRIVATE_REGISTRY_URL con l'URL del tuo registry privato.
3. Tagga le immagini con l'URL del tuo registro privato:

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

4. Esegui il push delle immagini taggate nel tuo registro privato:

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

Se riesci a eseguire il pull delle immagini taggate dal tuo registry privato, la procedura è andata a buon fine.

1.23.0

Per aggiungere le immagini a un registry privato, completa i seguenti passaggi:

1. Esegui il pull delle immagini di Config Sync:

   docker pull gcr.io/config-management-release/admission-webhook:v1.23.0-rc.1
   docker pull gcr.io/config-management-release/gcenode-askpass-sidecar:v1.23.0-rc.1
   docker pull gcr.io/config-management-release/git-sync:v4.4.2-gke.5__linux_amd64
   docker pull gcr.io/config-management-release/helm-sync:v1.23.0-rc.1
   docker pull gcr.io/config-management-release/hydration-controller:v1.23.0-rc.1
   docker pull gcr.io/config-management-release/oci-sync:v1.23.0-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.23.0-rc.1
   docker pull gcr.io/config-management-release/reconciler:v1.23.0-rc.1
   docker pull gcr.io/config-management-release/resource-group-controller:v1.23.0-rc.1
   

2. Crea una variabile per l'URL del tuo registry privato:

   export PRIVATE_REGISTRY_URL=PRIVATE_REGISTRY_URL
   

   Sostituisci PRIVATE_REGISTRY_URL con l'URL del tuo registry privato.
3. Tagga le immagini con l'URL del tuo registro privato:

   docker tag gcr.io/config-management-release/admission-webhook:v1.23.0-rc.1 \
    ${PRIVATE_REGISTRY_URL}/admission-webhook:v1.23.0-rc.1
   docker tag gcr.io/config-management-release/gcenode-askpass-sidecar:v1.23.0-rc.1 \
    ${PRIVATE_REGISTRY_URL}/gcenode-askpass-sidecar:v1.23.0-rc.1
   docker tag gcr.io/config-management-release/git-sync:v4.4.2-gke.5__linux_amd64 \
    ${PRIVATE_REGISTRY_URL}/git-sync:v4.4.2-gke.5__linux_amd64
   docker tag gcr.io/config-management-release/helm-sync:v1.23.0-rc.1 \
    ${PRIVATE_REGISTRY_URL}/helm-sync:v1.23.0-rc.1
   docker tag gcr.io/config-management-release/hydration-controller:v1.23.0-rc.1 \
    ${PRIVATE_REGISTRY_URL}/hydration-controller:v1.23.0-rc.1
   docker tag gcr.io/config-management-release/oci-sync:v1.23.0-rc.1 \
    ${PRIVATE_REGISTRY_URL}/oci-sync:v1.23.0-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.23.0-rc.1 \
    ${PRIVATE_REGISTRY_URL}/reconciler-manager:v1.23.0-rc.1
   docker tag gcr.io/config-management-release/reconciler:v1.23.0-rc.1 \
    ${PRIVATE_REGISTRY_URL}/reconciler:v1.23.0-rc.1
   docker tag gcr.io/config-management-release/resource-group-controller:v1.23.0-rc.1 \
    ${PRIVATE_REGISTRY_URL}/resource-group-controller:v1.23.0-rc.1
   

4. Esegui il push delle immagini taggate nel tuo registro privato:

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

Se riesci a eseguire il pull delle immagini taggate dal tuo registry privato, la procedura è andata a buon fine.