A partir da versão 1.12 da Apigee híbrida, você precisa usar o Helm para gerenciar a instalação híbrida. O ambiente de execução apigeectl está descontinuado.
Instalações atuais: se você quiser gerenciar um cluster híbrido atual com o Helm
e ele já for gerenciado com apigeectl, migre o cluster para o gerenciamento
do Helm com A Ferramenta de migração Apigee híbrida do Helm.
Versão com suporte do Helm
A Apigee híbrida é compatível com o Helm v3.14.2+.
Gráficos do Helm para componentes da Apigee híbrida
Os componentes híbridos são instalados e gerenciados pelos gráficos do Helm a seguir. A tabela é
organizada na ordem em que você normalmente as instala durante uma nova instalação.
Escopo
Componentes
Gráfico do Helm
Operador da Apigee
Operador da Apigee
apigee-operator
Armazenamento
Cassandra
apigee-datastore
Armazenamento na memória
Redis
apigee-redis
Relatórios
Métricas do logger
apigee-telemetry
Entrada
Gateway de entrada da Apigee
apigee-ingress-manager
Organização
Apigee Connect Agent MART UDCA Watcher
apigee-org
Ambiente
Sincronizador de ambiente de execução
apigee-env
Grupo de ambientes
virtualhost
apigee-virtualhost
apigeectl / Referência cruzada do comando Helm
A tabela a seguir lista os equivalentes do Helm para comandos apigeectl comuns:
Não existe um comando único para gerenciar todos os componentes híbridos. Como cada componente tem um gráfico específico, é necessário instalar ou fazer upgrade de cada gráfico individualmente.
Não há um comando Helm equivalente, mas é possível usar o processo Verificar a prontidão do cluster para executar várias das mesmas tarefas durante a instalação.
[[["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\u003eStarting with Apigee hybrid version 1.12, Helm is required for managing hybrid installations, and \u003ccode\u003eapigeectl\u003c/code\u003e is no longer supported.\u003c/p\u003e\n"],["\u003cp\u003eNew installations should begin with the "big picture" guide and then proceed with either Helm or \u003ccode\u003eapigeectl\u003c/code\u003e instructions from the hybrid runtime setup section.\u003c/p\u003e\n"],["\u003cp\u003eExisting installations that are currently managed with \u003ccode\u003eapigeectl\u003c/code\u003e must be migrated to Helm using the Apigee hybrid Helm migration tool if they wish to transition.\u003c/p\u003e\n"],["\u003cp\u003eApigee hybrid components are installed and managed using specific Helm charts, including \u003ccode\u003eapigee-operator\u003c/code\u003e, \u003ccode\u003eapigee-datastore\u003c/code\u003e, \u003ccode\u003eapigee-redis\u003c/code\u003e, \u003ccode\u003eapigee-telemetry\u003c/code\u003e, \u003ccode\u003eapigee-ingress-manager\u003c/code\u003e, \u003ccode\u003eapigee-org\u003c/code\u003e, \u003ccode\u003eapigee-env\u003c/code\u003e, and \u003ccode\u003eapigee-virtualhost\u003c/code\u003e.\u003c/p\u003e\n"],["\u003cp\u003eThere is no single Helm command that mirrors \u003ccode\u003eapigeectl apply\u003c/code\u003e or \u003ccode\u003eapigeectl delete --all\u003c/code\u003e, meaning each component or environment must be managed individually with its own respective Helm command.\u003c/p\u003e\n"]]],[],null,["# Apigee hybrid Helm reference\n\n| You are currently viewing version 1.12 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\nStarting in Apigee hybrid version 1.12, you need to use Helm to manage your hybrid installation. `apigeectl` is deprecated.\n\n- **New installations:** Start your installation with the instructions in [The big picture](/apigee/docs/hybrid/v1.12/big-picture), and then choose the instructions for either Helm or `apigeectl` in [Part 2: Hybrid runtime setup](/apigee/docs/hybrid/v1.12/install-before-begin).\n- **Existing installations:** If you want to manage an existing hybrid cluster with Helm and the cluster is already managed with `apigeectl`, migrate the cluster to Helm management with [The Apigee hybrid Helm migration tool](/apigee/docs/hybrid/v1.12/helm-migration).\n\nHelm supported version\n----------------------\n\n\nApigee hybrid supports Helm v3.14.2+.\n\nHelm charts for Apigee hybrid components\n----------------------------------------\n\n\nThe hybrid components are installed and managed by the following Helm charts. The table is\narranged in the order you will typically install them in during a fresh installation.\n\n| **Note:** The hybrid Helm charts depend on the Apigee hybrid Custom Resource Definitions (CRDs) being installed. See [Install the\n| Apigee hybrid CRDs](/apigee/docs/hybrid/v1.12/install-crds) in the Installation guide.\n\n`apigeectl` / Helm command cross reference\n------------------------------------------\n\n\nThe following table lists the Helm equivalents for common `apigeectl` commands:"]]
