## an example of internal component vs 3rd party
containers:
- name: apigee-udca
image: private-docker-host.example.com/apigee-udca:1.11.2
imagePullPolicy: IfNotPresent
containers:
- name: apigee-ingressgateway
image: private-docker-host.example.com/apigee-asm-ingress:1.17.2-asm.8-distroless
imagePullPolicy: IfNotPresent
[[["容易理解","easyToUnderstand","thumb-up"],["確實解決了我的問題","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["難以理解","hardToUnderstand","thumb-down"],["資訊或程式碼範例有誤","incorrectInformationOrSampleCode","thumb-down"],["缺少我需要的資訊/範例","missingTheInformationSamplesINeed","thumb-down"],["翻譯問題","translationIssue","thumb-down"],["其他","otherDown","thumb-down"]],["上次更新時間：2025-07-10 (世界標準時間)。"],[[["This documentation guides you through configuring Apigee hybrid to utilize images from a private container image repository instead of the default Google Cloud Container Registry."],["Apigee hybrid runtime images are typically hosted in the Google Cloud Container Registry (GCR), but you can download and push them to your private repository if needed."],["You can configure the use of a private repository by setting the `hub` configuration property with the path to your private repository."],["Using the provided `hub` value will automatically resolve the image paths for both internal Apigee components, as well as 3rd party components."],["The document also provides instructions on how to display a list of Apigee images hosted in the Google Cloud repository via command line."]]],[]]
