The hybrid components are installed and managed by the following Helm charts. The table is
arranged in the order you will typically install them in during a fresh installation.
Scope
Components
Helm chart
Apigee operator
Apigee operator
apigee-operator
Storage
Cassandra
apigee-datastore
In‑memory storage
Redis
apigee-redis
Reporting
Logger Metrics
apigee-telemetry
Ingress
Apigee Ingress gateway
apigee-ingress-manager
Organization
Apigee Connect Agent MART UDCA Watcher
apigee-org
Environment
Runtime Synchronizer
apigee-env
Environment group
virtualhost
apigee-virtualhost
apigeectl / Helm command cross reference
The following table lists the Helm equivalents for common apigeectl commands:
There is no single command to manage all hybrid components. Because each
component has a specific chart, you must install or upgrade each chart individually.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-20 UTC."],[[["\u003cp\u003eApigee hybrid supports Helm version 3.14.2 and above for managing its components.\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\u003eThe \u003ccode\u003eapigeectl init\u003c/code\u003e command is mimicked in Helm by installing or upgrading the \u003ccode\u003eapigee-operator\u003c/code\u003e and \u003ccode\u003eapigee-ingress-manager\u003c/code\u003e charts, which requires the Apigee CRDs to be installed first.\u003c/p\u003e\n"],["\u003cp\u003eThere is no single Helm command to manage all Apigee hybrid components at once, as each component needs to be installed or upgraded individually using its corresponding chart, similarly there is no single Helm command to delete all components.\u003c/p\u003e\n"],["\u003cp\u003eEquivalent Helm commands, like \u003ccode\u003ehelm install\u003c/code\u003e or \u003ccode\u003ehelm upgrade\u003c/code\u003e, are available for most \u003ccode\u003eapigeectl\u003c/code\u003e commands such as \u003ccode\u003eapply\u003c/code\u003e, \u003ccode\u003edelete\u003c/code\u003e, or \u003ccode\u003edry-run\u003c/code\u003e, enabling granular control over individual components, while \u003ccode\u003eapigeectl check-ready\u003c/code\u003e does not have an exact equivalent command, but relies on checking cluster readiness.\u003c/p\u003e\n"]]],[],null,[]]
