Aggiorna Config Sync utilizzando un registro privato

Ogni versione di Config Sync richiede un insieme specifico di immagini con controllo della versione per poter funzionare. Se utilizzi un registry privato, devi eseguire il pull, il tagging e il push di queste immagini nel tuo 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 durante la procedura di configurazione del cluster di amministrazione di Google Distributed Cloud. Config Sync rileva automaticamente quando è stato configurato un registro privato e si assicura che venga utilizzato da Config Sync. Per saperne di più, consulta Creare un cluster amministrativo nella documentazione di Google Distributed Cloud.

Avviso: esiste un problema noto in cui i deployment di reconciler non sono configurati correttamente per utilizzare il registry privato. Questo problema è stato risolto nella versione 1.19.0.

Aggiungere immagini a un registry privato

Per eseguire il push di immagini Config Sync specifiche della versione in un registry privato, fai clic sull'icona 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.20.1

Per aggiungere le immagini a un registry privato:

1. Estrai le immagini di Config Sync:

   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. 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 registry privato:

   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. Esegui il push delle immagini taggate nel tuo registry privato:

   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
   

Se riesci a estrarre le immagini taggate dal tuo registry privato, la procedura è andata a buon fine.

1.20.0

Per aggiungere le immagini a un registry privato:

1. Estrai le immagini di Config Sync:

   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. 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 registry privato:

   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. Esegui il push delle immagini taggate nel tuo registry privato:

   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
   

Se riesci a estrarre le immagini taggate dal tuo registry privato, la procedura è andata a buon fine.

1.19.2

Per aggiungere le immagini a un registry privato:

1. Estrai le immagini di Config Sync:

   docker pull gcr.io/config-management-release/config-management-operator:v1.19.2-rc.1
   docker pull gcr.io/config-management-release/admission-webhook:v1.19.2-rc.1
   docker pull gcr.io/config-management-release/gcenode-askpass-sidecar:v1.19.2-rc.1
   docker pull gcr.io/config-management-release/git-sync:v4.2.4-gke.8__linux_amd64
   docker pull gcr.io/config-management-release/gke-hc-manager:v0.11.0-hc.14
   docker pull gcr.io/config-management-release/helm-sync:v1.19.2-rc.1
   docker pull gcr.io/config-management-release/hnc-manager:hnc-v0.8.0-hc.16
   docker pull gcr.io/config-management-release/hydration-controller:v1.19.2-rc.1
   docker pull gcr.io/config-management-release/oci-sync:v1.19.2-rc.1
   docker pull gcr.io/config-management-release/otelcontribcol:v0.103.0-gke.4
   docker pull gcr.io/config-management-release/reconciler-manager:v1.19.2-rc.1
   docker pull gcr.io/config-management-release/reconciler:v1.19.2-rc.1
   docker pull gcr.io/config-management-release/resource-group-controller:v1.19.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 registry privato:

   docker tag gcr.io/config-management-release/config-management-operator:v1.19.2-rc.1 \
    ${PRIVATE_REGISTRY_URL}/config-management-operator:v1.19.2-rc.1
   docker tag gcr.io/config-management-release/admission-webhook:v1.19.2-rc.1 \
    ${PRIVATE_REGISTRY_URL}/admission-webhook:v1.19.2-rc.1
   docker tag gcr.io/config-management-release/gcenode-askpass-sidecar:v1.19.2-rc.1 \
    ${PRIVATE_REGISTRY_URL}/gcenode-askpass-sidecar:v1.19.2-rc.1
   docker tag gcr.io/config-management-release/git-sync:v4.2.4-gke.8__linux_amd64 \
    ${PRIVATE_REGISTRY_URL}/git-sync:v4.2.4-gke.8__linux_amd64
   docker tag gcr.io/config-management-release/gke-hc-manager:v0.11.0-hc.14 \
    ${PRIVATE_REGISTRY_URL}/gke-hc-manager:v0.11.0-hc.14
   docker tag gcr.io/config-management-release/helm-sync:v1.19.2-rc.1 \
    ${PRIVATE_REGISTRY_URL}/helm-sync:v1.19.2-rc.1
   docker tag gcr.io/config-management-release/hnc-manager:hnc-v0.8.0-hc.16 \
    ${PRIVATE_REGISTRY_URL}/hnc-manager:hnc-v0.8.0-hc.16
   docker tag gcr.io/config-management-release/hydration-controller:v1.19.2-rc.1 \
    ${PRIVATE_REGISTRY_URL}/hydration-controller:v1.19.2-rc.1
   docker tag gcr.io/config-management-release/oci-sync:v1.19.2-rc.1 \
    ${PRIVATE_REGISTRY_URL}/oci-sync:v1.19.2-rc.1
   docker tag gcr.io/config-management-release/otelcontribcol:v0.103.0-gke.4 \
    ${PRIVATE_REGISTRY_URL}/otelcontribcol:v0.103.0-gke.4
   docker tag gcr.io/config-management-release/reconciler-manager:v1.19.2-rc.1 \
    ${PRIVATE_REGISTRY_URL}/reconciler-manager:v1.19.2-rc.1
   docker tag gcr.io/config-management-release/reconciler:v1.19.2-rc.1 \
    ${PRIVATE_REGISTRY_URL}/reconciler:v1.19.2-rc.1
   docker tag gcr.io/config-management-release/resource-group-controller:v1.19.2-rc.1 \
    ${PRIVATE_REGISTRY_URL}/resource-group-controller:v1.19.2-rc.1
   

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

   docker push ${PRIVATE_REGISTRY_URL}/config-management-operator:v1.19.2-rc.1
   docker push ${PRIVATE_REGISTRY_URL}/admission-webhook:v1.19.2-rc.1
   docker push ${PRIVATE_REGISTRY_URL}/gcenode-askpass-sidecar:v1.19.2-rc.1
   docker push ${PRIVATE_REGISTRY_URL}/git-sync:v4.2.4-gke.8__linux_amd64
   docker push ${PRIVATE_REGISTRY_URL}/gke-hc-manager:v0.11.0-hc.14
   docker push ${PRIVATE_REGISTRY_URL}/helm-sync:v1.19.2-rc.1
   docker push ${PRIVATE_REGISTRY_URL}/hnc-manager:hnc-v0.8.0-hc.16
   docker push ${PRIVATE_REGISTRY_URL}/hydration-controller:v1.19.2-rc.1
   docker push ${PRIVATE_REGISTRY_URL}/oci-sync:v1.19.2-rc.1
   docker push ${PRIVATE_REGISTRY_URL}/otelcontribcol:v0.103.0-gke.4
   docker push ${PRIVATE_REGISTRY_URL}/reconciler-manager:v1.19.2-rc.1
   docker push ${PRIVATE_REGISTRY_URL}/reconciler:v1.19.2-rc.1
   docker push ${PRIVATE_REGISTRY_URL}/resource-group-controller:v1.19.2-rc.1
   

Se riesci a estrarre le immagini taggate dal tuo registry privato, la procedura è andata a buon fine.

1.19.1

Per aggiungere le immagini a un registry privato:

1. Estrai le immagini di Config Sync:

   docker pull gcr.io/config-management-release/config-management-operator:v1.19.1-rc.1
   docker pull gcr.io/config-management-release/admission-webhook:v1.19.1-rc.1
   docker pull gcr.io/config-management-release/gcenode-askpass-sidecar:v1.19.1-rc.1
   docker pull gcr.io/config-management-release/git-sync:v4.2.4-gke.4__linux_amd64
   docker pull gcr.io/config-management-release/gke-hc-manager:v0.11.0-hc.14
   docker pull gcr.io/config-management-release/helm-sync:v1.19.1-rc.1
   docker pull gcr.io/config-management-release/hnc-manager:hnc-v0.8.0-hc.16
   docker pull gcr.io/config-management-release/hydration-controller:v1.19.1-rc.1
   docker pull gcr.io/config-management-release/oci-sync:v1.19.1-rc.1
   docker pull gcr.io/config-management-release/otelcontribcol:v0.103.0-gke.4
   docker pull gcr.io/config-management-release/reconciler-manager:v1.19.1-rc.1
   docker pull gcr.io/config-management-release/reconciler:v1.19.1-rc.1
   docker pull gcr.io/config-management-release/resource-group-controller:v1.19.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 registry privato:

   docker tag gcr.io/config-management-release/config-management-operator:v1.19.1-rc.1 \
    ${PRIVATE_REGISTRY_URL}/config-management-operator:v1.19.1-rc.1
   docker tag gcr.io/config-management-release/admission-webhook:v1.19.1-rc.1 \
    ${PRIVATE_REGISTRY_URL}/admission-webhook:v1.19.1-rc.1
   docker tag gcr.io/config-management-release/gcenode-askpass-sidecar:v1.19.1-rc.1 \
    ${PRIVATE_REGISTRY_URL}/gcenode-askpass-sidecar:v1.19.1-rc.1
   docker tag gcr.io/config-management-release/git-sync:v4.2.4-gke.4__linux_amd64 \
    ${PRIVATE_REGISTRY_URL}/git-sync:v4.2.4-gke.4__linux_amd64
   docker tag gcr.io/config-management-release/gke-hc-manager:v0.11.0-hc.14 \
    ${PRIVATE_REGISTRY_URL}/gke-hc-manager:v0.11.0-hc.14
   docker tag gcr.io/config-management-release/helm-sync:v1.19.1-rc.1 \
    ${PRIVATE_REGISTRY_URL}/helm-sync:v1.19.1-rc.1
   docker tag gcr.io/config-management-release/hnc-manager:hnc-v0.8.0-hc.16 \
    ${PRIVATE_REGISTRY_URL}/hnc-manager:hnc-v0.8.0-hc.16
   docker tag gcr.io/config-management-release/hydration-controller:v1.19.1-rc.1 \
    ${PRIVATE_REGISTRY_URL}/hydration-controller:v1.19.1-rc.1
   docker tag gcr.io/config-management-release/oci-sync:v1.19.1-rc.1 \
    ${PRIVATE_REGISTRY_URL}/oci-sync:v1.19.1-rc.1
   docker tag gcr.io/config-management-release/otelcontribcol:v0.103.0-gke.4 \
    ${PRIVATE_REGISTRY_URL}/otelcontribcol:v0.103.0-gke.4
   docker tag gcr.io/config-management-release/reconciler-manager:v1.19.1-rc.1 \
    ${PRIVATE_REGISTRY_URL}/reconciler-manager:v1.19.1-rc.1
   docker tag gcr.io/config-management-release/reconciler:v1.19.1-rc.1 \
    ${PRIVATE_REGISTRY_URL}/reconciler:v1.19.1-rc.1
   docker tag gcr.io/config-management-release/resource-group-controller:v1.19.1-rc.1 \
    ${PRIVATE_REGISTRY_URL}/resource-group-controller:v1.19.1-rc.1
   

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

   docker push ${PRIVATE_REGISTRY_URL}/config-management-operator:v1.19.1-rc.1
   docker push ${PRIVATE_REGISTRY_URL}/admission-webhook:v1.19.1-rc.1
   docker push ${PRIVATE_REGISTRY_URL}/gcenode-askpass-sidecar:v1.19.1-rc.1
   docker push ${PRIVATE_REGISTRY_URL}/git-sync:v4.2.4-gke.4__linux_amd64
   docker push ${PRIVATE_REGISTRY_URL}/gke-hc-manager:v0.11.0-hc.14
   docker push ${PRIVATE_REGISTRY_URL}/helm-sync:v1.19.1-rc.1
   docker push ${PRIVATE_REGISTRY_URL}/hnc-manager:hnc-v0.8.0-hc.16
   docker push ${PRIVATE_REGISTRY_URL}/hydration-controller:v1.19.1-rc.1
   docker push ${PRIVATE_REGISTRY_URL}/oci-sync:v1.19.1-rc.1
   docker push ${PRIVATE_REGISTRY_URL}/otelcontribcol:v0.103.0-gke.4
   docker push ${PRIVATE_REGISTRY_URL}/reconciler-manager:v1.19.1-rc.1
   docker push ${PRIVATE_REGISTRY_URL}/reconciler:v1.19.1-rc.1
   docker push ${PRIVATE_REGISTRY_URL}/resource-group-controller:v1.19.1-rc.1
   

Se riesci a estrarre le immagini taggate dal tuo registry privato, la procedura è andata a buon fine.

1.19.0

Per aggiungere le immagini a un registry privato:

1. Estrai le immagini di Config Sync:

   docker pull gcr.io/config-management-release/config-management-operator:v1.19.0-rc.3
   docker pull gcr.io/config-management-release/admission-webhook:v1.19.0-rc.2
   docker pull gcr.io/config-management-release/gcenode-askpass-sidecar:v1.19.0-rc.2
   docker pull gcr.io/config-management-release/git-sync:v4.2.3-gke.5__linux_amd64
   docker pull gcr.io/config-management-release/gke-hc-manager:v0.11.0-hc.14
   docker pull gcr.io/config-management-release/helm-sync:v1.19.0-rc.2
   docker pull gcr.io/config-management-release/hnc-manager:hnc-v0.8.0-hc.16
   docker pull gcr.io/config-management-release/hydration-controller:v1.19.0-rc.2
   docker pull gcr.io/config-management-release/oci-sync:v1.19.0-rc.2
   docker pull gcr.io/config-management-release/otelcontribcol:v0.103.0-gke.3
   docker pull gcr.io/config-management-release/reconciler-manager:v1.19.0-rc.2
   docker pull gcr.io/config-management-release/reconciler:v1.19.0-rc.2
   docker pull gcr.io/config-management-release/resource-group-controller:v1.19.0-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 registry privato:

   docker tag gcr.io/config-management-release/config-management-operator:v1.19.0-rc.3 \
    ${PRIVATE_REGISTRY_URL}/config-management-operator:v1.19.0-rc.3
   docker tag gcr.io/config-management-release/admission-webhook:v1.19.0-rc.2 \
    ${PRIVATE_REGISTRY_URL}/admission-webhook:v1.19.0-rc.2
   docker tag gcr.io/config-management-release/gcenode-askpass-sidecar:v1.19.0-rc.2 \
    ${PRIVATE_REGISTRY_URL}/gcenode-askpass-sidecar:v1.19.0-rc.2
   docker tag gcr.io/config-management-release/git-sync:v4.2.3-gke.5__linux_amd64 \
    ${PRIVATE_REGISTRY_URL}/git-sync:v4.2.3-gke.5__linux_amd64
   docker tag gcr.io/config-management-release/gke-hc-manager:v0.11.0-hc.14 \
    ${PRIVATE_REGISTRY_URL}/gke-hc-manager:v0.11.0-hc.14
   docker tag gcr.io/config-management-release/helm-sync:v1.19.0-rc.2 \
    ${PRIVATE_REGISTRY_URL}/helm-sync:v1.19.0-rc.2
   docker tag gcr.io/config-management-release/hnc-manager:hnc-v0.8.0-hc.16 \
    ${PRIVATE_REGISTRY_URL}/hnc-manager:hnc-v0.8.0-hc.16
   docker tag gcr.io/config-management-release/hydration-controller:v1.19.0-rc.2 \
    ${PRIVATE_REGISTRY_URL}/hydration-controller:v1.19.0-rc.2
   docker tag gcr.io/config-management-release/oci-sync:v1.19.0-rc.2 \
    ${PRIVATE_REGISTRY_URL}/oci-sync:v1.19.0-rc.2
   docker tag gcr.io/config-management-release/otelcontribcol:v0.103.0-gke.3 \
    ${PRIVATE_REGISTRY_URL}/otelcontribcol:v0.103.0-gke.3
   docker tag gcr.io/config-management-release/reconciler-manager:v1.19.0-rc.2 \
    ${PRIVATE_REGISTRY_URL}/reconciler-manager:v1.19.0-rc.2
   docker tag gcr.io/config-management-release/reconciler:v1.19.0-rc.2 \
    ${PRIVATE_REGISTRY_URL}/reconciler:v1.19.0-rc.2
   docker tag gcr.io/config-management-release/resource-group-controller:v1.19.0-rc.2 \
    ${PRIVATE_REGISTRY_URL}/resource-group-controller:v1.19.0-rc.2
   

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

   docker push ${PRIVATE_REGISTRY_URL}/config-management-operator:v1.19.0-rc.3
   docker push ${PRIVATE_REGISTRY_URL}/admission-webhook:v1.19.0-rc.2
   docker push ${PRIVATE_REGISTRY_URL}/gcenode-askpass-sidecar:v1.19.0-rc.2
   docker push ${PRIVATE_REGISTRY_URL}/git-sync:v4.2.3-gke.5__linux_amd64
   docker push ${PRIVATE_REGISTRY_URL}/gke-hc-manager:v0.11.0-hc.14
   docker push ${PRIVATE_REGISTRY_URL}/helm-sync:v1.19.0-rc.2
   docker push ${PRIVATE_REGISTRY_URL}/hnc-manager:hnc-v0.8.0-hc.16
   docker push ${PRIVATE_REGISTRY_URL}/hydration-controller:v1.19.0-rc.2
   docker push ${PRIVATE_REGISTRY_URL}/oci-sync:v1.19.0-rc.2
   docker push ${PRIVATE_REGISTRY_URL}/otelcontribcol:v0.103.0-gke.3
   docker push ${PRIVATE_REGISTRY_URL}/reconciler-manager:v1.19.0-rc.2
   docker push ${PRIVATE_REGISTRY_URL}/reconciler:v1.19.0-rc.2
   docker push ${PRIVATE_REGISTRY_URL}/resource-group-controller:v1.19.0-rc.2
   

Se riesci a estrarre le immagini taggate dal tuo registry privato, la procedura è andata a buon fine.

1.18.3

Per aggiungere le immagini a un registry privato:

1. Estrai le immagini di Config Sync:

   docker pull gcr.io/config-management-release/config-management-operator:v1.18.3-rc.2
   docker pull gcr.io/config-management-release/admission-webhook:v1.18.3-rc.4
   docker pull gcr.io/config-management-release/gcenode-askpass-sidecar:v1.18.3-rc.4
   docker pull gcr.io/config-management-release/git-sync:v3.6.9-gke.21__linux_amd64
   docker pull gcr.io/config-management-release/git-sync:v4.2.3-gke.5__linux_amd64
   docker pull gcr.io/config-management-release/gke-hc-manager:v0.11.0-hc.14
   docker pull gcr.io/config-management-release/helm-sync:v1.18.3-rc.4
   docker pull gcr.io/config-management-release/hnc-manager:hnc-v0.8.0-hc.16
   docker pull gcr.io/config-management-release/hydration-controller:v1.18.3-rc.4
   docker pull gcr.io/config-management-release/monorepo:v1.18.3-rc.3
   docker pull gcr.io/config-management-release/oci-sync:v1.18.3-rc.4
   docker pull gcr.io/config-management-release/otelcontribcol:v0.102.0-gke.6
   docker pull gcr.io/config-management-release/reconciler-manager:v1.18.3-rc.4
   docker pull gcr.io/config-management-release/reconciler:v1.18.3-rc.4
   docker pull gcr.io/config-management-release/resource-group-controller:v1.18.3-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 registry privato:

   docker tag gcr.io/config-management-release/config-management-operator:v1.18.3-rc.2 \
    ${PRIVATE_REGISTRY_URL}/config-management-operator:v1.18.3-rc.2
   docker tag gcr.io/config-management-release/admission-webhook:v1.18.3-rc.4 \
    ${PRIVATE_REGISTRY_URL}/admission-webhook:v1.18.3-rc.4
   docker tag gcr.io/config-management-release/gcenode-askpass-sidecar:v1.18.3-rc.4 \
    ${PRIVATE_REGISTRY_URL}/gcenode-askpass-sidecar:v1.18.3-rc.4
   docker tag gcr.io/config-management-release/git-sync:v3.6.9-gke.21__linux_amd64 \
    ${PRIVATE_REGISTRY_URL}/git-sync:v3.6.9-gke.21__linux_amd64
   docker tag gcr.io/config-management-release/git-sync:v4.2.3-gke.5__linux_amd64 \
    ${PRIVATE_REGISTRY_URL}/git-sync:v4.2.3-gke.5__linux_amd64
   docker tag gcr.io/config-management-release/gke-hc-manager:v0.11.0-hc.14 \
    ${PRIVATE_REGISTRY_URL}/gke-hc-manager:v0.11.0-hc.14
   docker tag gcr.io/config-management-release/helm-sync:v1.18.3-rc.4 \
    ${PRIVATE_REGISTRY_URL}/helm-sync:v1.18.3-rc.4
   docker tag gcr.io/config-management-release/hnc-manager:hnc-v0.8.0-hc.16 \
    ${PRIVATE_REGISTRY_URL}/hnc-manager:hnc-v0.8.0-hc.16
   docker tag gcr.io/config-management-release/hydration-controller:v1.18.3-rc.4 \
    ${PRIVATE_REGISTRY_URL}/hydration-controller:v1.18.3-rc.4
   docker tag gcr.io/config-management-release/monorepo:v1.18.3-rc.3 \
    ${PRIVATE_REGISTRY_URL}/monorepo:v1.18.3-rc.3
   docker tag gcr.io/config-management-release/oci-sync:v1.18.3-rc.4 \
    ${PRIVATE_REGISTRY_URL}/oci-sync:v1.18.3-rc.4
   docker tag gcr.io/config-management-release/otelcontribcol:v0.102.0-gke.6 \
    ${PRIVATE_REGISTRY_URL}/otelcontribcol:v0.102.0-gke.6
   docker tag gcr.io/config-management-release/reconciler-manager:v1.18.3-rc.4 \
    ${PRIVATE_REGISTRY_URL}/reconciler-manager:v1.18.3-rc.4
   docker tag gcr.io/config-management-release/reconciler:v1.18.3-rc.4 \
    ${PRIVATE_REGISTRY_URL}/reconciler:v1.18.3-rc.4
   docker tag gcr.io/config-management-release/resource-group-controller:v1.18.3-rc.4 \
    ${PRIVATE_REGISTRY_URL}/resource-group-controller:v1.18.3-rc.4
   

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

   docker push ${PRIVATE_REGISTRY_URL}/config-management-operator:v1.18.3-rc.2
   docker push ${PRIVATE_REGISTRY_URL}/admission-webhook:v1.18.3-rc.4
   docker push ${PRIVATE_REGISTRY_URL}/gcenode-askpass-sidecar:v1.18.3-rc.4
   docker push ${PRIVATE_REGISTRY_URL}/git-sync:v3.6.9-gke.21__linux_amd64
   docker push ${PRIVATE_REGISTRY_URL}/git-sync:v4.2.3-gke.5__linux_amd64
   docker push ${PRIVATE_REGISTRY_URL}/gke-hc-manager:v0.11.0-hc.14
   docker push ${PRIVATE_REGISTRY_URL}/helm-sync:v1.18.3-rc.4
   docker push ${PRIVATE_REGISTRY_URL}/hnc-manager:hnc-v0.8.0-hc.16
   docker push ${PRIVATE_REGISTRY_URL}/hydration-controller:v1.18.3-rc.4
   docker push ${PRIVATE_REGISTRY_URL}/monorepo:v1.18.3-rc.3
   docker push ${PRIVATE_REGISTRY_URL}/oci-sync:v1.18.3-rc.4
   docker push ${PRIVATE_REGISTRY_URL}/otelcontribcol:v0.102.0-gke.6
   docker push ${PRIVATE_REGISTRY_URL}/reconciler-manager:v1.18.3-rc.4
   docker push ${PRIVATE_REGISTRY_URL}/reconciler:v1.18.3-rc.4
   docker push ${PRIVATE_REGISTRY_URL}/resource-group-controller:v1.18.3-rc.4
   

Se riesci a estrarre le immagini taggate dal tuo registry privato, la procedura è andata a buon fine.

1.18.2

Per aggiungere le immagini a un registry privato:

1. Estrai le immagini di Config Sync:

   docker pull gcr.io/config-management-release/config-management-operator:v1.18.2-rc.1
   docker pull gcr.io/config-management-release/admission-webhook:v1.18.2-rc.2
   docker pull gcr.io/config-management-release/gcenode-askpass-sidecar:v1.18.2-rc.2
   docker pull gcr.io/config-management-release/git-sync:v3.6.9-gke.15__linux_amd64
   docker pull gcr.io/config-management-release/git-sync:v4.2.1-gke.10__linux_amd64
   docker pull gcr.io/config-management-release/gke-hc-manager:v0.11.0-hc.13
   docker pull gcr.io/config-management-release/helm-sync:v1.18.2-rc.2
   docker pull gcr.io/config-management-release/hnc-manager:hnc-v0.8.0-hc.15
   docker pull gcr.io/config-management-release/hydration-controller:v1.18.2-rc.2
   docker pull gcr.io/config-management-release/monorepo:v1.18.2-rc.1
   docker pull gcr.io/config-management-release/oci-sync:v1.18.2-rc.2
   docker pull gcr.io/config-management-release/otelcontribcol:v0.102.0-gke.4
   docker pull gcr.io/config-management-release/reconciler-manager:v1.18.2-rc.2
   docker pull gcr.io/config-management-release/reconciler:v1.18.2-rc.2
   docker pull gcr.io/config-management-release/resource-group-controller:v1.18.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 registry privato:

   docker tag gcr.io/config-management-release/config-management-operator:v1.18.2-rc.1 \
    ${PRIVATE_REGISTRY_URL}/config-management-operator:v1.18.2-rc.1
   docker tag gcr.io/config-management-release/admission-webhook:v1.18.2-rc.2 \
    ${PRIVATE_REGISTRY_URL}/admission-webhook:v1.18.2-rc.2
   docker tag gcr.io/config-management-release/gcenode-askpass-sidecar:v1.18.2-rc.2 \
    ${PRIVATE_REGISTRY_URL}/gcenode-askpass-sidecar:v1.18.2-rc.2
   docker tag gcr.io/config-management-release/git-sync:v3.6.9-gke.15__linux_amd64 \
    ${PRIVATE_REGISTRY_URL}/git-sync:v3.6.9-gke.15__linux_amd64
   docker tag gcr.io/config-management-release/git-sync:v4.2.1-gke.10__linux_amd64 \
    ${PRIVATE_REGISTRY_URL}/git-sync:v4.2.1-gke.10__linux_amd64
   docker tag gcr.io/config-management-release/gke-hc-manager:v0.11.0-hc.13 \
    ${PRIVATE_REGISTRY_URL}/gke-hc-manager:v0.11.0-hc.13
   docker tag gcr.io/config-management-release/helm-sync:v1.18.2-rc.2 \
    ${PRIVATE_REGISTRY_URL}/helm-sync:v1.18.2-rc.2
   docker tag gcr.io/config-management-release/hnc-manager:hnc-v0.8.0-hc.15 \
    ${PRIVATE_REGISTRY_URL}/hnc-manager:hnc-v0.8.0-hc.15
   docker tag gcr.io/config-management-release/hydration-controller:v1.18.2-rc.2 \
    ${PRIVATE_REGISTRY_URL}/hydration-controller:v1.18.2-rc.2
   docker tag gcr.io/config-management-release/monorepo:v1.18.2-rc.1 \
    ${PRIVATE_REGISTRY_URL}/monorepo:v1.18.2-rc.1
   docker tag gcr.io/config-management-release/oci-sync:v1.18.2-rc.2 \
    ${PRIVATE_REGISTRY_URL}/oci-sync:v1.18.2-rc.2
   docker tag gcr.io/config-management-release/otelcontribcol:v0.102.0-gke.4 \
    ${PRIVATE_REGISTRY_URL}/otelcontribcol:v0.102.0-gke.4
   docker tag gcr.io/config-management-release/reconciler-manager:v1.18.2-rc.2 \
    ${PRIVATE_REGISTRY_URL}/reconciler-manager:v1.18.2-rc.2
   docker tag gcr.io/config-management-release/reconciler:v1.18.2-rc.2 \
    ${PRIVATE_REGISTRY_URL}/reconciler:v1.18.2-rc.2
   docker tag gcr.io/config-management-release/resource-group-controller:v1.18.2-rc.2 \
    ${PRIVATE_REGISTRY_URL}/resource-group-controller:v1.18.2-rc.2
   

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

   docker push ${PRIVATE_REGISTRY_URL}/config-management-operator:v1.18.2-rc.1
   docker push ${PRIVATE_REGISTRY_URL}/admission-webhook:v1.18.2-rc.2
   docker push ${PRIVATE_REGISTRY_URL}/gcenode-askpass-sidecar:v1.18.2-rc.2
   docker push ${PRIVATE_REGISTRY_URL}/git-sync:v3.6.9-gke.15__linux_amd64
   docker push ${PRIVATE_REGISTRY_URL}/git-sync:v4.2.1-gke.10__linux_amd64
   docker push ${PRIVATE_REGISTRY_URL}/gke-hc-manager:v0.11.0-hc.13
   docker push ${PRIVATE_REGISTRY_URL}/helm-sync:v1.18.2-rc.2
   docker push ${PRIVATE_REGISTRY_URL}/hnc-manager:hnc-v0.8.0-hc.15
   docker push ${PRIVATE_REGISTRY_URL}/hydration-controller:v1.18.2-rc.2
   docker push ${PRIVATE_REGISTRY_URL}/monorepo:v1.18.2-rc.1
   docker push ${PRIVATE_REGISTRY_URL}/oci-sync:v1.18.2-rc.2
   docker push ${PRIVATE_REGISTRY_URL}/otelcontribcol:v0.102.0-gke.4
   docker push ${PRIVATE_REGISTRY_URL}/reconciler-manager:v1.18.2-rc.2
   docker push ${PRIVATE_REGISTRY_URL}/reconciler:v1.18.2-rc.2
   docker push ${PRIVATE_REGISTRY_URL}/resource-group-controller:v1.18.2-rc.2
   

Se riesci a estrarre le immagini taggate dal tuo registry privato, la procedura è andata a buon fine.

1.18.1

Per aggiungere le immagini a un registry privato:

1. Estrai le immagini di Config Sync:

   docker pull gcr.io/config-management-release/config-management-operator:v1.18.1-rc.1
   docker pull gcr.io/config-management-release/admission-webhook:v1.18.1-rc.1
   docker pull gcr.io/config-management-release/gcenode-askpass-sidecar:v1.18.1-rc.1
   docker pull gcr.io/config-management-release/git-sync:v3.6.9-gke.15__linux_amd64
   docker pull gcr.io/config-management-release/git-sync:v4.2.1-gke.10__linux_amd64
   docker pull gcr.io/config-management-release/gke-hc-manager:v0.11.0-hc.13
   docker pull gcr.io/config-management-release/helm-sync:v1.18.1-rc.1
   docker pull gcr.io/config-management-release/hnc-manager:hnc-v0.8.0-hc.15
   docker pull gcr.io/config-management-release/hydration-controller:v1.18.1-rc.1
   docker pull gcr.io/config-management-release/monorepo:v1.18.1-rc.1
   docker pull gcr.io/config-management-release/oci-sync:v1.18.1-rc.1
   docker pull gcr.io/config-management-release/otelcontribcol:v0.99.0-gke.1
   docker pull gcr.io/config-management-release/reconciler-manager:v1.18.1-rc.1
   docker pull gcr.io/config-management-release/reconciler:v1.18.1-rc.1
   docker pull gcr.io/config-management-release/resource-group-controller:v1.18.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 registry privato:

   docker tag gcr.io/config-management-release/config-management-operator:v1.18.1-rc.1 \
    ${PRIVATE_REGISTRY_URL}/config-management-operator:v1.18.1-rc.1
   docker tag gcr.io/config-management-release/admission-webhook:v1.18.1-rc.1 \
    ${PRIVATE_REGISTRY_URL}/admission-webhook:v1.18.1-rc.1
   docker tag gcr.io/config-management-release/gcenode-askpass-sidecar:v1.18.1-rc.1 \
    ${PRIVATE_REGISTRY_URL}/gcenode-askpass-sidecar:v1.18.1-rc.1
   docker tag gcr.io/config-management-release/git-sync:v3.6.9-gke.15__linux_amd64 \
    ${PRIVATE_REGISTRY_URL}/git-sync:v3.6.9-gke.15__linux_amd64
   docker tag gcr.io/config-management-release/git-sync:v4.2.1-gke.10__linux_amd64 \
    ${PRIVATE_REGISTRY_URL}/git-sync:v4.2.1-gke.10__linux_amd64
   docker tag gcr.io/config-management-release/gke-hc-manager:v0.11.0-hc.13 \
    ${PRIVATE_REGISTRY_URL}/gke-hc-manager:v0.11.0-hc.13
   docker tag gcr.io/config-management-release/helm-sync:v1.18.1-rc.1 \
    ${PRIVATE_REGISTRY_URL}/helm-sync:v1.18.1-rc.1
   docker tag gcr.io/config-management-release/hnc-manager:hnc-v0.8.0-hc.15 \
    ${PRIVATE_REGISTRY_URL}/hnc-manager:hnc-v0.8.0-hc.15
   docker tag gcr.io/config-management-release/hydration-controller:v1.18.1-rc.1 \
    ${PRIVATE_REGISTRY_URL}/hydration-controller:v1.18.1-rc.1
   docker tag gcr.io/config-management-release/monorepo:v1.18.1-rc.1 \
    ${PRIVATE_REGISTRY_URL}/monorepo:v1.18.1-rc.1
   docker tag gcr.io/config-management-release/oci-sync:v1.18.1-rc.1 \
    ${PRIVATE_REGISTRY_URL}/oci-sync:v1.18.1-rc.1
   docker tag gcr.io/config-management-release/otelcontribcol:v0.99.0-gke.1 \
    ${PRIVATE_REGISTRY_URL}/otelcontribcol:v0.99.0-gke.1
   docker tag gcr.io/config-management-release/reconciler-manager:v1.18.1-rc.1 \
    ${PRIVATE_REGISTRY_URL}/reconciler-manager:v1.18.1-rc.1
   docker tag gcr.io/config-management-release/reconciler:v1.18.1-rc.1 \
    ${PRIVATE_REGISTRY_URL}/reconciler:v1.18.1-rc.1
   docker tag gcr.io/config-management-release/resource-group-controller:v1.18.1-rc.1 \
    ${PRIVATE_REGISTRY_URL}/resource-group-controller:v1.18.1-rc.1
   

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

   docker push ${PRIVATE_REGISTRY_URL}/config-management-operator:v1.18.1-rc.1
   docker push ${PRIVATE_REGISTRY_URL}/admission-webhook:v1.18.1-rc.1
   docker push ${PRIVATE_REGISTRY_URL}/gcenode-askpass-sidecar:v1.18.1-rc.1
   docker push ${PRIVATE_REGISTRY_URL}/git-sync:v3.6.9-gke.15__linux_amd64
   docker push ${PRIVATE_REGISTRY_URL}/git-sync:v4.2.1-gke.10__linux_amd64
   docker push ${PRIVATE_REGISTRY_URL}/gke-hc-manager:v0.11.0-hc.13
   docker push ${PRIVATE_REGISTRY_URL}/helm-sync:v1.18.1-rc.1
   docker push ${PRIVATE_REGISTRY_URL}/hnc-manager:hnc-v0.8.0-hc.15
   docker push ${PRIVATE_REGISTRY_URL}/hydration-controller:v1.18.1-rc.1
   docker push ${PRIVATE_REGISTRY_URL}/monorepo:v1.18.1-rc.1
   docker push ${PRIVATE_REGISTRY_URL}/oci-sync:v1.18.1-rc.1
   docker push ${PRIVATE_REGISTRY_URL}/otelcontribcol:v0.99.0-gke.1
   docker push ${PRIVATE_REGISTRY_URL}/reconciler-manager:v1.18.1-rc.1
   docker push ${PRIVATE_REGISTRY_URL}/reconciler:v1.18.1-rc.1
   docker push ${PRIVATE_REGISTRY_URL}/resource-group-controller:v1.18.1-rc.1
   

Se riesci a estrarre le immagini taggate dal tuo registry privato, la procedura è andata a buon fine.

1.18.0

Per aggiungere le immagini a un registry privato:

1. Estrai le immagini di Config Sync:

   docker pull gcr.io/config-management-release/config-management-operator:v1.18.0-rc.1
   docker pull gcr.io/config-management-release/admission-webhook:v1.18.0-rc.3
   docker pull gcr.io/config-management-release/gcenode-askpass-sidecar:v1.18.0-rc.3
   docker pull gcr.io/config-management-release/git-sync:v3.6.9-gke.13__linux_amd64
   docker pull gcr.io/config-management-release/git-sync:v4.2.1-gke.3__linux_amd64
   docker pull gcr.io/config-management-release/gke-hc-manager:v0.11.0-hc.12
   docker pull gcr.io/config-management-release/helm-sync:v1.18.0-rc.3
   docker pull gcr.io/config-management-release/hnc-manager:hnc-v0.8.0-hc.14
   docker pull gcr.io/config-management-release/hydration-controller:v1.18.0-rc.3
   docker pull gcr.io/config-management-release/monorepo:v1.18.0-rc.1
   docker pull gcr.io/config-management-release/oci-sync:v1.18.0-rc.3
   docker pull gcr.io/config-management-release/otelcontribcol:v0.91.0-gke.9
   docker pull gcr.io/config-management-release/reconciler-manager:v1.18.0-rc.3
   docker pull gcr.io/config-management-release/reconciler:v1.18.0-rc.3
   docker pull gcr.io/config-management-release/resource-group-controller:v1.18.0-rc.3
   

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 registry privato:

   docker tag gcr.io/config-management-release/config-management-operator:v1.18.0-rc.1 \
    ${PRIVATE_REGISTRY_URL}/config-management-operator:v1.18.0-rc.1
   docker tag gcr.io/config-management-release/admission-webhook:v1.18.0-rc.3 \
    ${PRIVATE_REGISTRY_URL}/admission-webhook:v1.18.0-rc.3
   docker tag gcr.io/config-management-release/gcenode-askpass-sidecar:v1.18.0-rc.3 \
    ${PRIVATE_REGISTRY_URL}/gcenode-askpass-sidecar:v1.18.0-rc.3
   docker tag gcr.io/config-management-release/git-sync:v3.6.9-gke.13__linux_amd64 \
    ${PRIVATE_REGISTRY_URL}/git-sync:v3.6.9-gke.13__linux_amd64
   docker tag gcr.io/config-management-release/git-sync:v4.2.1-gke.3__linux_amd64 \
    ${PRIVATE_REGISTRY_URL}/git-sync:v4.2.1-gke.3__linux_amd64
   docker tag gcr.io/config-management-release/gke-hc-manager:v0.11.0-hc.12 \
    ${PRIVATE_REGISTRY_URL}/gke-hc-manager:v0.11.0-hc.12
   docker tag gcr.io/config-management-release/helm-sync:v1.18.0-rc.3 \
    ${PRIVATE_REGISTRY_URL}/helm-sync:v1.18.0-rc.3
   docker tag gcr.io/config-management-release/hnc-manager:hnc-v0.8.0-hc.14 \
    ${PRIVATE_REGISTRY_URL}/hnc-manager:hnc-v0.8.0-hc.14
   docker tag gcr.io/config-management-release/hydration-controller:v1.18.0-rc.3 \
    ${PRIVATE_REGISTRY_URL}/hydration-controller:v1.18.0-rc.3
   docker tag gcr.io/config-management-release/monorepo:v1.18.0-rc.1 \
    ${PRIVATE_REGISTRY_URL}/monorepo:v1.18.0-rc.1
   docker tag gcr.io/config-management-release/oci-sync:v1.18.0-rc.3 \
    ${PRIVATE_REGISTRY_URL}/oci-sync:v1.18.0-rc.3
   docker tag gcr.io/config-management-release/otelcontribcol:v0.91.0-gke.9 \
    ${PRIVATE_REGISTRY_URL}/otelcontribcol:v0.91.0-gke.9
   docker tag gcr.io/config-management-release/reconciler-manager:v1.18.0-rc.3 \
    ${PRIVATE_REGISTRY_URL}/reconciler-manager:v1.18.0-rc.3
   docker tag gcr.io/config-management-release/reconciler:v1.18.0-rc.3 \
    ${PRIVATE_REGISTRY_URL}/reconciler:v1.18.0-rc.3
   docker tag gcr.io/config-management-release/resource-group-controller:v1.18.0-rc.3 \
    ${PRIVATE_REGISTRY_URL}/resource-group-controller:v1.18.0-rc.3
   

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

   docker push ${PRIVATE_REGISTRY_URL}/config-management-operator:v1.18.0-rc.1
   docker push ${PRIVATE_REGISTRY_URL}/config-management-operator:v1.18.0-rc.1
   docker push ${PRIVATE_REGISTRY_URL}/admission-webhook:v1.18.0-rc.3
   docker push ${PRIVATE_REGISTRY_URL}/gcenode-askpass-sidecar:v1.18.0-rc.3
   docker push ${PRIVATE_REGISTRY_URL}/git-sync:v3.6.9-gke.13__linux_amd64
   docker push ${PRIVATE_REGISTRY_URL}/git-sync:v4.2.1-gke.3__linux_amd64
   docker push ${PRIVATE_REGISTRY_URL}/gke-hc-manager:v0.11.0-hc.12
   docker push ${PRIVATE_REGISTRY_URL}/helm-sync:v1.18.0-rc.3
   docker push ${PRIVATE_REGISTRY_URL}/hnc-manager:hnc-v0.8.0-hc.14
   docker push ${PRIVATE_REGISTRY_URL}/hydration-controller:v1.18.0-rc.3
   docker push ${PRIVATE_REGISTRY_URL}/monorepo:v1.18.0-rc.1
   docker push ${PRIVATE_REGISTRY_URL}/oci-sync:v1.18.0-rc.3
   docker push ${PRIVATE_REGISTRY_URL}/otelcontribcol:v0.91.0-gke.9
   docker push ${PRIVATE_REGISTRY_URL}/reconciler-manager:v1.18.0-rc.3
   docker push ${PRIVATE_REGISTRY_URL}/reconciler:v1.18.0-rc.3
   docker push ${PRIVATE_REGISTRY_URL}/resource-group-controller:v1.18.0-rc.3
   

Se riesci a estrarre le immagini taggate dal tuo registry privato, la procedura è andata a buon fine.