Tutte le immagini di runtime ibride sono disponibili pubblicamente per il download da Google Container Registry.
Scaricare le immagini container
Se utilizzi un cluster Kubernetes senza accesso a internet per eseguire il deployment dei servizi di runtime ibrido, dovrai scaricare le immagini dei container in un registry dei container locale e poi accedere al registry dal tuo cluster Kubernetes.
Per scaricare un'immagine container, devi avere installato Docker e utilizzare il comando docker pull come segue. Assicurati di aggiungere il tag corretto
a ogni nome dell'immagine. Ad esempio, il tag per apigee-synchronizer è 1.5.10, come mostrato di seguito.
Spazio dei nomi: apigee-system
docker pull gcr.io/apigee-release/hybrid/apigee-installer:1.5.10docker pull gcr.io/apigee-release/hybrid/apigee-kube-rbac-proxy:v0.11.0docker pull gcr.io/apigee-release/hybrid/apigee-operators:1.5.10
Spazio dei nomi: apigee
docker pull gcr.io/apigee-release/hybrid/apigee-authn-authz:1.5.10docker pull gcr.io/apigee-release/hybrid/apigee-cassandra-backup-utility:1.5.10docker pull gcr.io/apigee-release/hybrid/apigee-connect-agent:1.5.10docker pull gcr.io/apigee-release/hybrid/apigee-envoy:v1.19.1docker pull gcr.io/apigee-release/hybrid/apigee-fluent-bit:1.8.10docker pull gcr.io/apigee-release/hybrid/apigee-hybrid-cassandra-client:1.5.10docker pull gcr.io/apigee-release/hybrid/apigee-hybrid-cassandra:1.5.10docker pull gcr.io/apigee-release/hybrid/apigee-mart-server:1.5.10docker pull gcr.io/apigee-release/hybrid/apigee-prom-prometheus:v2.33.5docker pull gcr.io/apigee-release/hybrid/apigee-redis:1.5.10docker pull gcr.io/apigee-release/hybrid/apigee-runtime:1.5.10docker pull gcr.io/apigee-release/hybrid/apigee-stackdriver-logging-agent:1.8.4docker pull gcr.io/apigee-release/hybrid/apigee-stackdriver-prometheus-sidecar:0.7.5docker pull gcr.io/apigee-release/hybrid/apigee-synchronizer:1.5.10docker pull gcr.io/apigee-release/hybrid/apigee-udca:1.5.10docker pull gcr.io/apigee-release/hybrid/apigee-watcher:1.5.10