---
title: Install using a Helm chart
description: Starting from ECK 1.3.0, a Helm chart is available to install ECK. It is available from the Elastic Helm repository and can be added to your Helm repository...
url: https://docs-v3-preview.elastic.dev/elastic/docs-content/pull/4491/deploy-manage/deploy/cloud-on-k8s/install-using-helm-chart
products:
  - Elastic Cloud on Kubernetes
---

# Install using a Helm chart
Starting from ECK 1.3.0, a Helm chart is available to install ECK. It is available from the Elastic Helm repository and can be added to your Helm repository list by running the following command:
```sh
helm repo add elastic https://helm.elastic.co
helm repo update
```

<note>
  The minimum supported version of Helm is 3.2.0.
</note>


## Installation options

The Elastic Operator Helm chart supports two main installation methods:
- Cluster-wide (global) installation – Installs both the operator and all its Custom Resource Definitions (CRDs) in a single step.
- Restricted installation – Separates the installation of the CRDs from the operator, allowing multiple operator instances to coexist in the same cluster while managing different sets of namespaces.

A restricted installation is required if you plan to run multiple operators in the same cluster or if the operator cannot have cluster-wide permissions.

### Cluster-wide (global) installation

This is the default mode of installation and is equivalent to [installing ECK using the stand-alone YAML manifests](https://docs-v3-preview.elastic.dev/elastic/docs-content/pull/4491/deploy-manage/deploy/cloud-on-k8s/install-using-yaml-manifest-quickstart).
```sh
helm install elastic-operator elastic/eck-operator -n elastic-system --create-namespace
```


### Restricted installation

This mode avoids installing any cluster-scoped resources and restricts the operator to manage only a set of pre-defined namespaces.
Since CRDs are global resources, they still need to be installed by an administrator. This can be achieved by:
```sh
helm install elastic-operator-crds elastic/eck-operator-crds
```

The operator can be installed by any user who has full access to the set of namespaces they wish to manage. The following example installs the operator to `elastic-system` namespace and configures it to manage only `namespace-a` and `namespace-b`:
```sh
helm install elastic-operator elastic/eck-operator -n elastic-system --create-namespace \
  --set=installCRDs=false \
  --set=managedNamespaces='{namespace-a, namespace-b}' \
  --set=createClusterScopedResources=false \
  --set=webhook.enabled=false \
  --set=config.validateStorageClass=false
```

<note>
  The `eck-operator` chart contains several pre-defined profiles to help you install the operator in different configurations. These profiles can be found in the root of the chart directory, prefixed with `profile-`. For example, the restricted configuration illustrated in the previous code extract is defined in the `profile-restricted.yaml` file, and can be used as follows:
  ```sh
  helm install elastic-operator elastic/eck-operator -n elastic-system --create-namespace \
    --values="${CHART_DIR}/profile-restricted.yaml" \
    --set=managedNamespaces='{namespace-a, namespace-b}'
  ```
  You can find the profile files in the Helm cache directory or in the [ECK source repository](https://github.com/elastic/cloud-on-k8s/tree/3.2/deploy/eck-operator).
</note>

The previous example disabled the validation webhook along with all other cluster-wide resources. If you need to enable the validation webhook in a restricted environment, see [Webhook namespace selectors](https://docs-v3-preview.elastic.dev/elastic/docs-content/pull/4491/deploy-manage/deploy/cloud-on-k8s/webhook-namespace-selectors). To understand what the validation webhook does, refer to [Configure the validating webhook](https://docs-v3-preview.elastic.dev/elastic/docs-content/pull/4491/deploy-manage/deploy/cloud-on-k8s/configure-validating-webhook).

## View available configuration options

You can view all configurable values of the operator Helm chart by running the following:
```sh
helm show values elastic/eck-operator
```


## Migrate an existing installation to Helm

<warning>
  Migrating an existing installation to Helm is essentially an upgrade operation and any [caveats associated with normal operator upgrades](/elastic/docs-content/pull/4491/deploy-manage/upgrade/orchestrator/upgrade-cloud-on-k8s#k8s-beta-to-ga-rolling-restart) are applicable. Check the [upgrade documentation](/elastic/docs-content/pull/4491/deploy-manage/upgrade/orchestrator/upgrade-cloud-on-k8s#k8s-ga-upgrade) before proceeding.
</warning>

You can migrate an existing operator installation to Helm by adding the `meta.helm.sh/release-name`, `meta.helm.sh/release-namespace` annotations and the `app.kubernetes.io/managed-by` label to all the resources you want to be adopted by Helm. You *must* do this for the Elastic Custom Resource Definitions (CRD) because deleting them would trigger the deletion of all deployed Elastic applications as well. All other resources are optional and can be deleted.
<note>
  A shell script is available in the [ECK source repository](https://github.com/elastic/cloud-on-k8s/blob/3.2/deploy/helm-migrate.sh) to demonstrate how to migrate from version 1.7.1 to Helm. You can modify it to suit your own environment.
</note>

For example, an ECK 1.2.1 installation deployed using [YAML manifests](https://docs-v3-preview.elastic.dev/elastic/docs-content/pull/4491/deploy-manage/deploy/cloud-on-k8s/install-using-yaml-manifest-quickstart) can be migrated to Helm as follows:
1. Annotate and label all the ECK CRDs with the appropriate Helm annotations and labels. CRDs need to be preserved to retain any existing Elastic applications deployed using the operator.
   ```sh
   for CRD in $(kubectl get crds --no-headers -o custom-columns=NAME:.metadata.name | grep k8s.elastic.co); do
       kubectl annotate crd "$CRD" meta.helm.sh/release-name="$RELEASE_NAME"
       kubectl annotate crd "$CRD" meta.helm.sh/release-namespace="$RELEASE_NAMESPACE"
       kubectl label crd "$CRD" app.kubernetes.io/managed-by=Helm
   done
   ```
2. Uninstall the current ECK operator. You can do this by taking the `operator.yaml` file you used to install the operator and running `kubectl delete -f operator.yaml`. Alternatively, you could delete each resource individually.
   ```sh
   kubectl delete -n elastic-system \
       serviceaccount/elastic-operator \
       secret/elastic-webhook-server-cert \
       clusterrole.rbac.authorization.k8s.io/elastic-operator \
       clusterrole.rbac.authorization.k8s.io/elastic-operator-view \
       clusterrole.rbac.authorization.k8s.io/elastic-operator-edit \
       clusterrolebinding.rbac.authorization.k8s.io/elastic-operator \
       service/elastic-webhook-server \
       configmap/elastic-operator \ 
       statefulset.apps/elastic-operator \
       validatingwebhookconfiguration.admissionregistration.k8s.io/elastic-webhook.k8s.elastic.co
   ```
3. Install the ECK operator using the Helm chart as described in [Install ECK using the Helm chart](https://docs-v3-preview.elastic.dev/elastic/docs-content/pull/4491/deploy-manage/deploy/cloud-on-k8s/install-using-helm-chart).


## Next steps

- For ECK configuration settings, refer to [Configure ECK](https://docs-v3-preview.elastic.dev/elastic/docs-content/pull/4491/deploy-manage/deploy/cloud-on-k8s/configure).
- To continue with the installation of Elasticsearch and Kibana go to [Manage deployments in Elastic Cloud on Kubernetes](https://docs-v3-preview.elastic.dev/elastic/docs-content/pull/4491/deploy-manage/deploy/cloud-on-k8s/manage-deployments).