Apigee hybrid Helm reference Stay organized with collections Save and categorize content based on your preferences.
You are currently viewing version 1.14 of the Apigee hybrid documentation. For more information, seeSupported versions.
Note: The hybrid Helm charts depend on the Apigee hybrid Custom Resource Definitions (CRDs) being installed. SeeInstall theApigee hybrid CRDs in the Installation guide.
Helm supported version
Apigee hybrid supports Helm v3.14.2+.
Helm charts for Apigee hybrid components
The hybrid components are installed and managed by the following Helm charts. The table isarranged 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 commonapigeectl commands:
apigeectl command | Helm command |
|---|---|
apigeectl init | The following commands mimicapigeectl init:
For example: kubectl apply -k apigee-operator/etc/crds/default/ |
apigeectl init when used to install or apply changes to istiod. |
For example: helm upgrade ingress-manager apigee-ingress-manager/ \ --install \ --namespaceAPIGEE_NAMESPACE \ --atomic \ -foverrides.yaml |
apigeectl apply | There is no single command to manage all hybrid components. Because each component hasa specific chart, you must install or upgrade each chart individually. |
apigeectl apply --datastore |
For example: helm upgrade datastore apigee-datastore/ \ --install \ --namespaceAPIGEE_NAMESPACE \ --atomic \ -foverrides.yaml |
apigeectl apply --redis |
For example: helm upgrade redis apigee-redis/ \ --install \ --namespaceAPIGEE_NAMESPACE \ --atomic \ -foverrides.yaml |
apigeectl apply --org |
For example: helm upgrade$ORG_NAME apigee-org/ \ --install \ --namespaceAPIGEE_NAMESPACE \ --atomic \ -foverrides.yaml |
apigeectl apply --envENV_NAME |
For example: helm upgrade$ENV_NAME apigee-env/ \ --install \ --namespaceAPIGEE_NAMESPACE \ --set env=ENV_NAME \--atomic \ -foverrides.yaml |
apigeectl apply --all-envs | There is no single command to manage all environments at once. You must install or upgrade eachenvironment individually. |
apigeectl apply --settings virtualhosts |
For example: helm upgrade$ENV_GROUP apigee-virtualhosts/ \ --install \ --namespaceAPIGEE_NAMESPACE \--set envgroup=$ENV_GROUP \ --atomic \ -foverrides.yaml |
apigeectl deleteCOMPONENT |
For example: helm delete datastore -nAPIGEE_NAMESPACE |
apigeectl delete orapigeectl delete --all | There is no single Helm command to delete all components at once. You must delete eachcomponent individually. |
apigeectlCOMMAND --dry-run=client |
For example: helm upgrade datastore apigee-datastore/ \ --install \ --namespaceAPIGEE_NAMESPACE \ --atomic \ -foverrides.yaml \ --dry-run=server |
apigeectl check-ready | There is no equivalent Helm command. |
Except as otherwise noted, the content of this page is licensed under theCreative Commons Attribution 4.0 License, and code samples are licensed under theApache 2.0 License. For details, see theGoogle Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.
Last updated 2026-02-19 UTC.