Ogni versione di Config Sync richiede un insieme specifico di immagini con controllo delle versioni per l'esecuzione. Se utilizzi un registro privato, devi eseguire il pull, il tagging e il push di queste immagini nel registro privato prima di poter installare i componenti di Config Sync o eseguire l'upgrade della versione di Config Sync.
Aggiungere immagini a un registro privato
Per eseguire il push delle immagini di Config Sync specifiche della versione in un registro privato, fai clic sull'icona Più per la versione che vuoi utilizzare e completa i passaggi elencati.
1.24.3
Per aggiungere le immagini a un registro privato, completa i seguenti passaggi:
-
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
-
Crea una variabile per l'URL del registro privato:
export PRIVATE_REGISTRY_URL=PRIVATE_REGISTRY_URL
PRIVATE_REGISTRY_URLcon l'URL del registro privato. -
Tagga le immagini con l'URL del 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 - Esegui il push delle immagini taggate nel 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 registro privato, la procedura è andata a buon fine.
1.24.2
Per aggiungere le immagini a un registro privato, completa i seguenti passaggi:
-
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
-
Crea una variabile per l'URL del registro privato:
export PRIVATE_REGISTRY_URL=PRIVATE_REGISTRY_URL
PRIVATE_REGISTRY_URLcon l'URL del registro privato. -
Tagga le immagini con l'URL del 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 - Esegui il push delle immagini taggate nel 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 registro privato, la procedura è andata a buon fine.
1.24.1
Per aggiungere le immagini a un registro privato, completa i seguenti passaggi:
-
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
-
Crea una variabile per l'URL del registro privato:
export PRIVATE_REGISTRY_URL=PRIVATE_REGISTRY_URL
PRIVATE_REGISTRY_URLcon l'URL del registro privato. -
Tagga le immagini con l'URL del 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 - Esegui il push delle immagini taggate nel 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 registro privato, la procedura è andata a buon fine.
1.24.0
Per aggiungere le immagini a un registro privato, completa i seguenti passaggi:
-
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
-
Crea una variabile per l'URL del registro privato:
export PRIVATE_REGISTRY_URL=PRIVATE_REGISTRY_URL
PRIVATE_REGISTRY_URLcon l'URL del registro privato. -
Tagga le immagini con l'URL del 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 - Esegui il push delle immagini taggate nel 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 registro privato, la procedura è andata a buon fine.
1.23.3
Per aggiungere le immagini a un registro privato, completa i seguenti passaggi:
-
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
-
Crea una variabile per l'URL del registro privato:
export PRIVATE_REGISTRY_URL=PRIVATE_REGISTRY_URL
PRIVATE_REGISTRY_URLcon l'URL del registro privato. -
Tagga le immagini con l'URL del 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 - Esegui il push delle immagini taggate nel 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 registro privato, la procedura è andata a buon fine.
1.23.2
Per aggiungere le immagini a un registro privato, completa i seguenti passaggi:
-
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
-
Crea una variabile per l'URL del registro privato:
export PRIVATE_REGISTRY_URL=PRIVATE_REGISTRY_URL
PRIVATE_REGISTRY_URLcon l'URL del registro privato. -
Tagga le immagini con l'URL del 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 - Esegui il push delle immagini taggate nel 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 registro privato, la procedura è andata a buon fine.
1.23.1
Per aggiungere le immagini a un registro privato, completa i seguenti passaggi:
-
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
-
Crea una variabile per l'URL del registro privato:
export PRIVATE_REGISTRY_URL=PRIVATE_REGISTRY_URL
PRIVATE_REGISTRY_URLcon l'URL del registro privato. -
Tagga le immagini con l'URL del 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 - Esegui il push delle immagini taggate nel 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 registro privato, la procedura è andata a buon fine.
1.23.0
Per aggiungere le immagini a un registro privato, completa i seguenti passaggi:
-
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
-
Crea una variabile per l'URL del registro privato:
export PRIVATE_REGISTRY_URL=PRIVATE_REGISTRY_URL
PRIVATE_REGISTRY_URLcon l'URL del registro privato. -
Tagga le immagini con l'URL del 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 - Esegui il push delle immagini taggate nel 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 registro privato, la procedura è andata a buon fine.
1.22.2
Per aggiungere le immagini a un registro privato, completa i seguenti passaggi:
-
Esegui il pull delle immagini di Config Sync:
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
-
Crea una variabile per l'URL del registro privato:
export PRIVATE_REGISTRY_URL=PRIVATE_REGISTRY_URL
PRIVATE_REGISTRY_URLcon l'URL del registro privato. -
Tagga le immagini con l'URL del registro privato:
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 - Esegui il push delle immagini taggate nel registro privato:
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
Se riesci a eseguire il pull delle immagini taggate dal registro privato, la procedura è andata a buon fine.
1.22.1
Per aggiungere le immagini a un registro privato, completa i seguenti passaggi:
-
Esegui il pull delle immagini di Config Sync:
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
-
Crea una variabile per l'URL del registro privato:
export PRIVATE_REGISTRY_URL=PRIVATE_REGISTRY_URL
PRIVATE_REGISTRY_URLcon l'URL del registro privato. -
Tagga le immagini con l'URL del registro privato:
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 - Esegui il push delle immagini taggate nel registro privato:
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
Se riesci a eseguire il pull delle immagini taggate dal registro privato, la procedura è andata a buon fine.
1.22.0
Per aggiungere le immagini a un registro privato, completa i seguenti passaggi:
-
Esegui il pull delle immagini di Config Sync:
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
-
Crea una variabile per l'URL del registro privato:
export PRIVATE_REGISTRY_URL=PRIVATE_REGISTRY_URL
PRIVATE_REGISTRY_URLcon l'URL del registro privato. -
Tagga le immagini con l'URL del registro privato:
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 - Esegui il push delle immagini taggate nel registro privato:
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
Se riesci a eseguire il pull delle immagini taggate dal registro privato, la procedura è andata a buon fine.