Dokumen ini menjelaskan cara mengonfigurasi Apigee hybrid untuk menggunakan image dari repositori image container pribadi.
Ringkasan
Semua image runtime campuran Apigee dihosting di
Google Cloud Container Registry (GCR). Jika karena alasan apa pun Anda ingin menggunakan repositori penampung image pribadi,
Anda dapat mendownload image dari GCR, mendorongnya ke repositori pribadi, dan mengganti
lokasi image default dalam file overrides.yaml.
Langkah konfigurasi
Ikuti langkah-langkah berikut untuk menggunakan repositori penampung image pribadi untuk image campuran Apigee. Untuk
melakukan langkah-langkah ini dan berhasil menggunakan image di repositori pribadi, Anda harus memahami
prosedur penginstalan hibrida Apigee. Dalam skenario
umum, Anda akan berencana mengonfigurasi repositori pribadi sebagai bagian dari penginstalan campuran baru.
Kirim image campuran Apigee dari GCR ke repositori pribadi Anda. Sebaiknya gunakan utilitas
apigee-push-pull untuk menyelesaikan langkah ini.
Jika Anda memilih untuk melakukan langkah ini secara manual, Anda harus menginstal Docker dan menggunakan perintah docker pull sebagai berikut. Pastikan untuk menambahkan tag yang benar
ke setiap nama gambar. Misalnya, tag untuk apigee-synchronizer adalah 1.9.4,
seperti yang ditunjukkan di bawah.
Berikut adalah gambar untuk namespace apigee-system dan apigee:
Tambahkan Secret ke file overrides.yaml Anda. Pembuatan file penggantian dijelaskan dalam langkah-langkah penginstalan hybrid. Lihat Mengonfigurasi cluster untuk mengetahui detailnya.
imagePullSecrets:
- name: SECRET_NAME
Perbarui file overrides.yaml dengan URL gambar untuk gambar yang disimpan di repositori pribadi Anda. Setiap komponen yang disimpan di repositori memiliki elemen image:url. Gunakan elemen ini untuk menentukan URL setiap gambar komponen. Contoh:
Ikuti pola ini untuk memperbarui setiap komponen campuran tingkat atas dalam file overrides.yaml dengan
URL image repositori pribadinya. Contoh lengkap file penggantian disediakan dengan penginstalan campuran Anda di
direktori
$APIGEECTL_HOME/examples/private-overrides.yaml.
Sekarang Anda dapat menyelesaikan penginstalan campuran baru menggunakan image pribadi, atau mengupdate penginstalan
yang ada. Lihat langkah-langkah penginstalan Apigee Hybrid untuk mengetahui informasi selengkapnya.
Menginstal cert-manager dari repositori pribadi
Untuk menginstal cert-manager dari repositori pribadi, lihat Menginstal dengan Helm.
Anda harus menginstal cert-manager versi yang sama seperti yang ditentukan dalam petunjuk penginstalan Apigee Hybrid untuk memastikan kompatibilitas.
[[["Mudah dipahami","easyToUnderstand","thumb-up"],["Memecahkan masalah saya","solvedMyProblem","thumb-up"],["Lainnya","otherUp","thumb-up"]],[["Sulit dipahami","hardToUnderstand","thumb-down"],["Informasi atau kode contoh salah","incorrectInformationOrSampleCode","thumb-down"],["Informasi/contoh yang saya butuhkan tidak ada","missingTheInformationSamplesINeed","thumb-down"],["Masalah terjemahan","translationIssue","thumb-down"],["Lainnya","otherDown","thumb-down"]],["Terakhir diperbarui pada 2025-09-04 UTC."],[[["\u003cp\u003eThis document details the process of configuring Apigee hybrid to utilize images from a private container image repository instead of the default Google Cloud Container Registry (GCR).\u003c/p\u003e\n"],["\u003cp\u003eTo use a private repository, you must first pull the required Apigee hybrid images from GCR, tag them appropriately, and then push them to your chosen private repository.\u003c/p\u003e\n"],["\u003cp\u003eA Kubernetes Secret containing your private repository credentials needs to be created in both the \u003ccode\u003eapigee\u003c/code\u003e and \u003ccode\u003eapigee-system\u003c/code\u003e namespaces within your cluster.\u003c/p\u003e\n"],["\u003cp\u003eYou must modify the \u003ccode\u003eoverrides.yaml\u003c/code\u003e file to include the created Secret and to update each component's image URL to point to its location in your private repository.\u003c/p\u003e\n"],["\u003cp\u003eYou may also use the utility \u003ccode\u003eapigee-pull-push\u003c/code\u003e for pushing the images to the private repository and update the \u003ccode\u003eoverrides.yaml\u003c/code\u003e file for a fresh install or an update to the current one.\u003c/p\u003e\n"]]],[],null,["# Use a private image repository\n\n| You are currently viewing version 1.9 of the Apigee hybrid documentation. **This version is end of life.** You should upgrade to a newer version. For more information, see [Supported versions](/apigee/docs/hybrid/supported-platforms#supported-versions).\n\n\nThis document explains how to configure Apigee hybrid to use images from a private container image repository.\n\nOverview\n--------\n\n\nAll Apigee hybrid runtime images are hosted in the [Google Cloud Container Registry](https://cloud.google.com/container-registry/) (GCR). If for any reason you wish to employ a private image container repository,\nyou can download the images from GCR, push them to your private repository, and override\nthe default image locations in your `overrides.yaml` file.\n\nConfiguration steps\n-------------------\n\n\nFollow these steps to use a private image container repository for the Apigee hybrid images. To\nperform these steps and successfully use the images in your private repository, you must be familiar\nwith the [Apigee hybrid installation procedure](./install-before-begin). In a typical\nscenario, you would plan to configure the private repository as part of a fresh hybrid installation.\n\n1. Push the Apigee hybrid images from GCR to your private repository. We recommend that you use the [apigee-push-pull](/apigee/docs/hybrid/v1.9/apigee-pull-push) utility to accomplish this step.\n\n If you prefer to do this step manually, you need to have [Docker](https://docs.docker.com/get-started/)\n installed and use the `docker pull` command as follows. Be sure to append the correct tag\n to each image name. For example, the tag for `apigee-synchronizer` is `1.9.4`,\n as shown below.\n | **Note:** You can get an up to date list of all images in your current project with the `--list` option of the [`apigee-pull-push.sh` utility](/apigee/docs/hybrid/v1.9/apigee-pull-push) in the `apigeectl/tools/` directory: \n |\n | ```\n | apigee-pull-push.sh --list\n | ```\n\n\n Here are the images for the `apigee-system` and `apigee` namespaces:\n\n\n **Namespace: `apigee-system`** \n\n docker pull gcr.io/apigee-release/hybrid/apigee-installer:1.9.4\n docker pull gcr.io/apigee-release/hybrid/apigee-kube-rbac-proxy:v0.14.0\n docker pull gcr.io/apigee-release/hybrid/apigee-operators:1.9.4\n\n\n **Namespace: `apigee`** \n\n docker pull gcr.io/apigee-release/hybrid/apigee-cassandra-backup-utility:1.9.4\n docker pull gcr.io/apigee-release/hybrid/apigee-connect-agent:1.9.4\n docker pull gcr.io/apigee-release/hybrid/apigee-diagnostics-collector:1.9.4\n docker pull gcr.io/apigee-release/hybrid/apigee-envoy:v1.25.1\n docker pull gcr.io/apigee-release/hybrid/apigee-fluent-bit:2.1.3\n docker pull gcr.io/apigee-release/hybrid/apigee-hybrid-cassandra-client:1.9.4\n docker pull gcr.io/apigee-release/hybrid/apigee-hybrid-cassandra:1.9.4\n docker pull gcr.io/apigee-release/hybrid/apigee-mart-server:1.9.4\n docker pull gcr.io/apigee-release/hybrid/apigee-mint-task-scheduler:1.9.4\n docker pull gcr.io/apigee-release/hybrid/apigee-prom-prometheus:v2.39.1\n docker pull gcr.io/apigee-release/hybrid/apigee-prometheus-adapter:v0.10.0\n docker pull gcr.io/apigee-release/hybrid/apigee-redis:1.9.4\n docker pull gcr.io/apigee-release/hybrid/apigee-runtime:1.9.4\n docker pull gcr.io/apigee-release/hybrid/apigee-stackdriver-logging-agent:1.9.12-2\n docker pull gcr.io/apigee-release/hybrid/apigee-stackdriver-prometheus-sidecar:0.9.0\n docker pull gcr.io/apigee-release/hybrid/apigee-synchronizer:1.9.4\n docker pull gcr.io/apigee-release/hybrid/apigee-udca:1.9.4\n docker pull gcr.io/apigee-release/hybrid/apigee-watcher:1.9.4\n docker pull gcr.io/apigee-release/hybrid/apigee-asm-ingress:1.17.2-asm.8-distroless\n docker pull gcr.io/apigee-release/hybrid/apigee-asm-istiod:1.17.2-asm.8-distroless\n\n\n After you pull and tag the images, you must push them to your private repository. See [docker push](https://docs.docker.com/engine/reference/commandline/push/).\n2. Create a Kubernetes Secret in the `apigee` and `apigee-system` namespaces.\n\n If these namespaces do not exist in your cluster, you must create them before performing this step.\n\n For steps to create the Secret, see [Create a Secret by providing credentials on the command line](https://kubernetes.io/docs/tasks/configure-pod-container/pull-image-private-registry/#create-a-secret-by-providing-credentials-on-the-command-line).\n For example, to create a secret in the `apigee-system` namespace: \n\n ```\n kubectl create secret docker-registry SECRET_NAME -n apigee-system \\\n --docker-server=YOUR_REGISTRY_SERVER \\\n --docker-username=YOUR_DOCKER_USERNAME \\\n --docker-email=YOUR_DOCKER_EMAIL \\\n --docker-password=\"YOUR_DOCKER_PASSWORD)\"\n ```\n\n\n To create a Secret in the `apigee` namespace: \n\n ```\n kubectl create secret docker-registry SECRET_NAME -n apigee \\\n --docker-server=YOUR_REGISTRY_SERVER \\\n --docker-username=YOUR_DOCKER_USERNAME \\\n --docker-email=YOUR_DOCKER_EMAIL \\\n --docker-password=\"YOUR_DOCKER_PASSWORD)\"\n ```\n3. Add the Secret to your `overrides.yaml` file. Creation of the overrides file is described in the hybrid installation steps. See [Configure the cluster](/apigee/docs/hybrid/v1.9/install-configure-cluster) for details. \n\n ```\n imagePullSecrets:\n - name: SECRET_NAME\n ```\n4. Update your `overrides.yaml` file with image URLs for the images stored in your private repository. Each component that is stored in the repository has an `image:url` element. Use this element to specify the URL of each component image. For example: \n\n ```\n mart:\n serviceAccountPath: /installdir/hybrid-files/service-accounts/hybrid-apigee-non-prod.json\n image:\n url: my-docker.pkg.dev/hybrid-1/registry-name/apigee-mart-server\n ```\n\n\n Follow this pattern to update each top-level hybrid component in your `overrides.yaml` file with its\n private repository image URL. A complete example overrides file is provided with your hybrid installation in\n **$APIGEECTL_HOME**`/examples/private-overrides.yaml`\n directory.\n | **Note:** You only need to update the `url` property. You can accept the default values for the `tag` and `pullPolicy` properties. For a complete list of components and their configuration properties, see also [Configuration property reference](./config-prop-ref).\n\n\nYou can now complete a new hybrid installation using the private images, or update your existing\ninstallation. See the [Apigee hybrid installation steps](./install-before-begin) for more information.\n\nInstalling cert-manager from a private repository\n-------------------------------------------------\n\n\nTo install `cert-manager` from your private repository, see [Installing with Helm](https://cert-manager.io/docs/installation/helm/).\nIt is important that you install the same version of `cert-manager` as specified\nin the [Apigee hybrid installation](./install-cert-manager) instructions to ensure compatibility."]]
