Utilizzare un repository di immagini private con Apigee hybrid

Version 1.15 (latest)

   Supported versions:

• v1.15 (latest)                        
• v1.14                        
• v1.13                         
• List of supported versions

   Unsupported versions:

• v1.12                         
• v1.11                         
• v1.10                                      
• v1.9                                         
• v1.8                                         
• v1.7                                         
• v1.6                                         
• v1.5                                         
• v1.4                                         
• v1.3                                         
• v1.2                                         
• v1.1                                         

Questo documento spiega come configurare Apigee Hybrid per utilizzare le immagini da un repository di immagini container privato.

Panoramica

Tutte le immagini di runtime ibrido di Apigee sono ospitate in Artifact Registry (AR). Se per qualsiasi motivo vuoi utilizzare un repository di container di immagini privato, puoi scaricare le immagini da AR e caricarle nel tuo repository privato. Anziché eseguire l'override di ogni componente, puoi aggiungere i dettagli dell'hub agli override:

Passaggi di configurazione

Imposta il valore della proprietà di configurazione hub con il percorso del tuo repository privato.

hub: PRIVATE_REPO

Ad esempio, se viene fornito il seguente hub, il percorso dell'immagine verrà risolto automaticamente:

hub: private-docker-host.example.com

come:

## an example of internal component vs 3rd party
containers:
- name: apigee-udca
  image: private-docker-host.example.com/apigee-udca:1.15.1
  imagePullPolicy: IfNotPresent

containers:
- name: apigee-ingressgateway
  image: private-docker-host.example.com/apigee-asm-ingress:1.22.6-asm.2-distroless
  imagePullPolicy: IfNotPresent

Fai clic per espandere un elenco di immagini Apigee

apigee:
    gcr.io/apigee-release/hybrid/apigee-mart-server:YOUR_HYBRID_VERSION_TAG
    gcr.io/apigee-release/hybrid/apigee-synchronizer:YOUR_HYBRID_VERSION_TAG
    gcr.io/apigee-release/hybrid/apigee-runtime:YOUR_HYBRID_VERSION_TAG
    gcr.io/apigee-release/hybrid/apigee-hybrid-cassandra-client:YOUR_HYBRID_VERSION_TAG
    gcr.io/apigee-release/hybrid/apigee-hybrid-cassandra:YOUR_HYBRID_VERSION_TAG
    gcr.io/apigee-release/hybrid/apigee-udca:YOUR_HYBRID_VERSION_TAG
    gcr.io/apigee-release/hybrid/apigee-connect-agent:YOUR_HYBRID_VERSION_TAG
    gcr.io/apigee-release/hybrid/apigee-watcher:YOUR_HYBRID_VERSION_TAG
    gcr.io/apigee-release/hybrid/apigee-operators:YOUR_HYBRID_VERSION_TAG
    gcr.io/apigee-release/hybrid/apigee-redis:YOUR_HYBRID_VERSION_TAG
    gcr.io/apigee-release/hybrid/apigee-mint-task-scheduler:YOUR_HYBRID_VERSION_TAG
third party:
    gcr.io/apigee-release/hybrid/apigee-stackdriver-logging-agent:YOUR_HYBRID_VERSION_TAG
    gcr.io/apigee-release/hybrid/apigee-prom-prometheus:YOUR_HYBRID_VERSION_TAG
    gcr.io/apigee-release/hybrid/apigee-stackdriver-prometheus-sidecar:YOUR_HYBRID_VERSION_TAG
    gcr.io/apigee-release/hybrid/apigee-kube-rbac-proxy:YOUR_HYBRID_VERSION_TAG
    gcr.io/apigee-release/hybrid/apigee-envoy:YOUR_HYBRID_VERSION_TAG
    gcr.io/apigee-release/hybrid/apigee-prometheus-adapter:YOUR_HYBRID_VERSION_TAG
    gcr.io/apigee-release/hybrid/apigee-asm-ingress:YOUR_HYBRID_VERSION_TAG
    gcr.io/apigee-release/hybrid/apigee-asm-istiod:YOUR_HYBRID_VERSION_TAG
    gcr.io/apigee-release/hybrid/apigee-fluent-bit:YOUR_HYBRID_VERSION_TAG
    gcr.io/apigee-release/hybrid/apigee-open-telemetry-collector:YOUR_HYBRID_VERSION_TAG

Puoi visualizzare il tag della versione originale delle immagini di terze parti come etichetta restituita dai comandi docker history o docker inspect.

Per visualizzare un elenco delle immagini Apigee ospitate nel repository Google Cloud, utilizza il comando apigee-pull-push:

./apigee-operator/etc/tools/apigee-pull-push.sh --list