Neste documento, explicamos como configurar a Apigee híbrida para usar imagens de um repositório de imagens de contêiner particular.
Visão geral
Todas as imagens de ambiente de execução híbrido da Apigee estão hospedadas no
Google Cloud Container Registry (GCR). Se por algum motivo você quiser empregar um repositório de contêineres de imagens particulares, é possível fazer o download das imagens do GCR, enviá-las ao seu repositório privado e substituir os locais padrão das imagens no arquivo overrides.yaml.
Etapas de configuração
Siga estas etapas para usar um repositório de contêineres de imagens particular para as imagens híbridas da Apigee. Para
realizar estas etapas e usar as imagens no seu repositório particular, você precisa conhecer
o procedimento de instalação híbrida da Apigee. Em um cenário
típico, você planeja configurar o repositório particular como parte de uma nova instalação híbrida.
Envie as imagens da Apigee híbrida do GCR para seu repositório particular. Recomendamos usar o
utilitário apigee-push-pull para essa etapa.
Se você preferir fazer isso manualmente, precisará ter o Docker
instalado e usar o comando docker pull da seguinte maneira. Anexe a tag correta
a cada nome de imagem. Por exemplo, a tag para apigee-synchronizer é 1.8.8,
conforme mostrado abaixo.
Veja as imagens para os namespaces apigee-system e apigee:
Adicione o secret ao seu arquivo overrides.yaml. A criação do arquivo de modificações
é descrita nas etapas de instalação híbrida. Consulte Configurar o cluster para mais detalhes.
imagePullSecrets:
- name: SECRET_NAME
Atualize seu arquivo overrides.yaml com os URLs das imagens armazenadas no seu repositório particular. Cada componente armazenado no repositório tem um elemento image:url. Use esse elemento para especificar o URL de cada imagem de componente. Exemplo:
Siga esse padrão para atualizar cada componente híbrido de nível superior no seu arquivo overrides.yaml com o
URL da imagem do repositório privado. Um exemplo completo de substituição de arquivo é fornecido com a instalação híbrida no diretório
$APIGEECTL_HOME/examples/private-overrides.yaml.
Agora é possível concluir uma nova instalação híbrida usando as imagens privadas ou atualizar a instalação atual. Consulte as etapas de instalação da Apigee híbrida para mais informações.
Como instalar o cert-manager de um repositório particular
Para instalar o cert-manager usando seu repositório particular, consulte Como instalar com o Helm.
Para garantir a compatibilidade, é importante instalar a mesma versão de cert-manager especificada
nas instruções de instalação híbrida da Apigee.
[[["Fácil de entender","easyToUnderstand","thumb-up"],["Meu problema foi resolvido","solvedMyProblem","thumb-up"],["Outro","otherUp","thumb-up"]],[["Difícil de entender","hardToUnderstand","thumb-down"],["Informações incorretas ou exemplo de código","incorrectInformationOrSampleCode","thumb-down"],["Não contém as informações/amostras de que eu preciso","missingTheInformationSamplesINeed","thumb-down"],["Problema na tradução","translationIssue","thumb-down"],["Outro","otherDown","thumb-down"]],["Última atualização 2025-08-28 UTC."],[[["\u003cp\u003eThis documentation explains how to configure Apigee hybrid to use images from a private container image repository instead of the default Google Cloud Container Registry.\u003c/p\u003e\n"],["\u003cp\u003eThe process involves pushing Apigee hybrid images from GCR to your private repository, either manually using Docker or with the \u003ccode\u003eapigee-pull-push\u003c/code\u003e utility.\u003c/p\u003e\n"],["\u003cp\u003eYou must create a Kubernetes Secret in both the \u003ccode\u003eapigee\u003c/code\u003e and \u003ccode\u003eapigee-system\u003c/code\u003e namespaces to allow access to your private repository.\u003c/p\u003e\n"],["\u003cp\u003eThe \u003ccode\u003eoverrides.yaml\u003c/code\u003e file needs to be updated to include the Secret and to specify the URLs for the images in the private repository, replacing the default GCR URLs.\u003c/p\u003e\n"],["\u003cp\u003eThis document pertains to Apigee hybrid version 1.8, which is end-of-life and should be upgraded to a newer version.\u003c/p\u003e\n"]]],[],null,["# Use a private image repository\n\n| You are currently viewing version 1.8 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.8/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.8.8`,\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.8/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.8.8\n docker pull gcr.io/apigee-release/hybrid/apigee-kube-rbac-proxy:v0.11.0\n docker pull gcr.io/apigee-release/hybrid/apigee-operators:1.8.8\n\n\n **Namespace: `apigee`** \n\n docker pull gcr.io/apigee-release/hybrid/apigee-cassandra-backup-utility:1.8.8\n docker pull gcr.io/apigee-release/hybrid/apigee-connect-agent:1.8.8\n docker pull gcr.io/apigee-release/hybrid/apigee-diagnostics-collector:1.8.8\n docker pull gcr.io/apigee-release/hybrid/apigee-envoy:v1.21.0\n docker pull gcr.io/apigee-release/hybrid/apigee-fluent-bit:1.9.9\n docker pull gcr.io/apigee-release/hybrid/apigee-hybrid-cassandra-client:1.8.8\n docker pull gcr.io/apigee-release/hybrid/apigee-hybrid-cassandra:1.8.8\n docker pull gcr.io/apigee-release/hybrid/apigee-mart-server:1.8.8\n docker pull gcr.io/apigee-release/hybrid/apigee-mint-task-scheduler:1.8.8\n docker pull gcr.io/apigee-release/hybrid/apigee-prom-prometheus:v2.33.5\n docker pull gcr.io/apigee-release/hybrid/apigee-prometheus-adapter:v0.9.1\n docker pull gcr.io/apigee-release/hybrid/apigee-redis:1.8.8\n docker pull gcr.io/apigee-release/hybrid/apigee-runtime:1.8.8\n docker pull gcr.io/apigee-release/hybrid/apigee-stackdriver-logging-agent:1.8.9\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.8.8\n docker pull gcr.io/apigee-release/hybrid/apigee-udca:1.8.8\n docker pull gcr.io/apigee-release/hybrid/apigee-watcher:1.8.8\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](./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."]]
