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:

helm repo add elastic https://helm.elastic.cohelm repo update

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.

This is the default mode of installation and is equivalent toinstalling ECK using the stand-alone YAML manifests.

helm install elastic-operator elastic/eck-operator -n elastic-system --create-namespace

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:

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 toelastic-system namespace and configures it to manage onlynamespace-a andnamespace-b:

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

helm install elastic-operator elastic/eck-operator -n elastic-system --create-namespace \  --values="${CHART_DIR}/profile-restricted.yaml" \  --set=managedNamespaces='{namespace-a, namespace-b}'

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, seeWebhook namespace selectors. To understand what the validation webhook does, refer toConfigure the validating webhook.

You can view all configurable values of the operator Helm chart by running the following:

helm show values elastic/eck-operator

You can migrate an existing operator installation to Helm by adding themeta.helm.sh/release-name,meta.helm.sh/release-namespace annotations and theapp.kubernetes.io/managed-by label to all the resources you want to be adopted by Helm. Youmust 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.

For example, an ECK 1.2.1 installation deployed usingYAML manifests 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.

   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=Helmdone

2. Uninstall the current ECK operator. You can do this by taking theoperator.yaml file you used to install the operator and runningkubectl delete -f operator.yaml. Alternatively, you could delete each resource individually.

   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

   1. If you have previously customized the operator configuration in this ConfigMap, you will have to repeat the configuration once the operator has been reinstalled in the next step.

3. Install the ECK operator using the Helm chart as described inInstall ECK using the Helm chart.

• For ECK configuration settings, refer toConfigure ECK.
• To continue with the installation of Elasticsearch and Kibana go toManage deployments in Elastic Cloud on Kubernetes.