> [!CAUTION]
> You are currently viewing version 1.11 of the Apigee hybrid documentation. **This version is end of life.** You should upgrade to a newer version. For more information, see [Supported versions](https://docs.cloud.google.com/apigee/docs/hybrid/supported-platforms.md.txt#supported-versions).

<button class="button button-with-icon cloud-select-dropdown__button button-primary" aria-haspopup="true">Version 1.11 </button>

- Supported versions:
- [v1.17 (latest)](https://docs.cloud.google.com/apigee/docs/hybrid/v1.17/helm-reference.md.txt)
- [v1.16](https://docs.cloud.google.com/apigee/docs/hybrid/v1.16/helm-reference.md.txt)
- [v1.15](https://docs.cloud.google.com/apigee/docs/hybrid/v1.15/helm-reference.md.txt)
- [v1.14](https://docs.cloud.google.com/apigee/docs/hybrid/v1.14/helm-reference.md.txt)
- [List of supported versions](https://docs.cloud.google.com/apigee/docs/hybrid/supported-platforms.md.txt#supported-versions)
- Unsupported versions:
- [v1.13](https://docs.cloud.google.com/apigee/docs/hybrid/v1.13/helm-reference.md.txt)
- [v1.12](https://docs.cloud.google.com/apigee/docs/hybrid/v1.12/helm-reference.md.txt)
- [v1.11](https://docs.cloud.google.com/apigee/docs/hybrid/v1.11/helm-reference.md.txt)
- [v1.10](https://docs.cloud.google.com/apigee/docs/hybrid/v1.10/helm-reference.html)
- [v1.9](https://docs.cloud.google.com/apigee/docs/hybrid/v1.9/helm-reference.html)
- [v1.8](https://docs.cloud.google.com/apigee/docs/hybrid/v1.8/helm-reference.html)
- [v1.7](https://docs.cloud.google.com/apigee/docs/hybrid/v1.7/helm-reference.html)
- [v1.6](https://docs.cloud.google.com/apigee/docs/hybrid/v1.6/helm-reference.html)
- [v1.5](https://docs.cloud.google.com/apigee/docs/hybrid/v1.5/helm-reference.html)
- [v1.4](https://docs.cloud.google.com/apigee/docs/hybrid/v1.4/helm-reference.html)
- [v1.3](https://docs.cloud.google.com/apigee/docs/hybrid/v1.3/helm-reference.html)
- [v1.2](https://docs.cloud.google.com/apigee/docs/hybrid/v1.2/helm-reference.html)
- [v1.1](https://docs.cloud.google.com/apigee/docs/hybrid/v1.1/helm-reference.html)


In Apigee hybrid version 1.11, you have the choice of installing and
managing your clusters with either Helm charts or `apigeectl`. You cannot manage a
cluster with both.

- **New installations:** Start your installation with the instructions in [The big picture](https://docs.cloud.google.com/apigee/docs/hybrid/v1.11/big-picture.md.txt), and then choose the instructions for either Helm or `apigeectl` in [Part 2: Hybrid runtime setup](https://docs.cloud.google.com/apigee/docs/hybrid/v1.11/install-before-begin.md.txt).
- **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](https://docs.cloud.google.com/apigee/docs/hybrid/v1.11/helm-migration.md.txt).

## Helm charts supported version


Apigee hybrid supports Helm charts v3.10+.

## Helm charts for Apigee hybrid components


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 Watcher | `apigee-org` |
| **Environment** | Runtime Synchronizer UDCA | `apigee-env` |
| **Environment group** | virtualhost | `apigee-virtualhost` |

> [!NOTE]
> **Note:** The hybrid Helm charts depend on the Apigee hybrid Custom Resource Definitions (CRDs) being installed. See [Install the
> Apigee hybrid CRDs](https://docs.cloud.google.com/apigee/docs/hybrid/v1.11/helm-install-crds) in the Installation guide.

## `apigeectl` / Helm command cross reference


The following table lists the Helm equivalents for common `apigeectl` commands:

| `apigeectl` command | Helm command |
|---|---|
| `apigeectl init` | The following commands mimic `apigeectl init`: - `kubectl apply -k apigee-operator/etc/crds/default/` - `helm install operator apigee-operator/` or `helm upgrade operator apigee-operator/` - `helm install ingress-manager apigee-ingress-manager/` or `helm upgrade ingress-manager apigee-ingress-manager/` For example: kubectl apply -k  apigee-operator/etc/crds/default/ helm install operator apigee-operator/ --namespace apigee \ --atomic \ -f overrides.yaml helm install ingress-manager apigee-ingress-manager/ --namespace apigee \ --atomic \ -f overrides.yaml |
| `apigeectl init` when used to install or apply changes to istiod. | - `helm install ingress-manager apigee-ingress-manager/` - `helm upgrade ingress-manager apigee-ingress-manager/` For example: ``` helm upgrade ingress-manager apigee-ingress-manager/ \ --install \ --namespace apigee \ --atomic \ -f overrides.yaml ``` |
| `apigeectl apply` | 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. |
| `apigeectl apply --datastore` | - `helm install datastore apigee-datastore/` - `helm upgrade datastore apigee-datastore/` For example: ``` helm upgrade datastore apigee-datastore/ \ --install \ --namespace apigee \ --atomic \ -f overrides.yaml ``` |
| `apigeectl apply --redis` | - `helm install redis apigee-redis/` - `helm upgrade redis apigee-redis/` For example: ``` helm upgrade redis apigee-redis/ \ --install \ --namespace apigee \ --atomic \ -f overrides.yaml ``` |
| `apigeectl apply --org` | - `helm install ORG_NAME apigee-org/` - `helm upgrade ORG_NAME apigee-org/` For example: ``` helm upgrade ORG_NAME apigee-org/ \ --install \ --namespace apigee \ --atomic \ -f overrides.yaml ``` |
| `apigeectl apply --env ENV_NAME` | - `helm install ENV_NAME apigee-env/` - `helm upgrade ENV_NAME apigee-env/` For example: ``` helm upgrade ENV_NAME apigee-env/ \ --install \ --namespace apigee \ --set env=ENV_NAME \ --atomic \ -f overrides.yaml ``` |
| `apigeectl apply --all-envs` | There is no single command to manage all environments at once. You must install or upgrade each environment individually. |
| `apigeectl apply --settings virtualhosts` | - `helm install ENV_GROUP_NAME apigee-virtualhosts/` - `helm upgrade ENV_GROUP_NAME apigee-virtualhosts/` For example: ``` helm upgrade ENV_GROUP_NAME apigee-virtualhosts/ \ --install \ --namespace apigee \ --set envgroup=ENV_GROUP_NAME \ --atomic \ -f overrides.yaml ``` > [!NOTE] > **Note:** You must install or upgrade each environment group individually. |
| `apigeectl delete COMPONENT` | - `helm delete RELEASE_NAME` For example: ``` helm delete datastore -n apigee ``` |
| `apigeectl delete` or `apigeectl delete --all` | There is no single Helm command to delete all components at once. You must delete each component individually. |
| `apigeectl COMMAND --dry-run=client` | - `helm COMMAND --dry-run` For example: ``` helm upgrade datastore apigee-datastore/ \ --install \ --namespace apigee \ --atomic \ -f overrides.yaml \ --dry-run ``` |
| `apigeectl check-ready` | While there is no no equivalent Helm command, during installation You can use the [Check cluster readiness](https://docs.cloud.google.com/apigee/docs/hybrid/v1.11/helm-install-check-cluster.md.txt) process to perform many of the same tasks. |