add migration section

Author: kaitlynmichael

content/operate/kubernetes/deployment/helm.md

@@ -12,8 +12,6 @@ weight: 11
 
 Helm charts provide a simple way to install the Redis Enterprise for Kubernetes operator in just a few steps. For more information about Helm, go to [https://helm.sh/docs/](https://helm.sh/docs/).
 
-{{<note>}} This feature is currently in public preview and is not supported on production workloads. Only new installations of the Redis operator are supported at this time. The steps for [creating the RedisEnterpriseCluster (REC)]({{<relref "operate/kubernetes/deployment/quick-start#create-a-redis-enterprise-cluster-rec">}}) and other custom resources remain the same.{{</note>}}
-
 ## Prerequisites
 
 - A [supported distribution]({{< relref "/operate/kubernetes/reference/supported_k8s_distributions" >}}) of Kubernetes.
@@ -35,14 +33,14 @@ The steps below use the following placeholders to indicate command line paramete
 
 1. Add the Redis repository.
 
-```sh
-helm repo add <repo-name> https://helm.redis.io/
-```
+   ```sh
+   helm repo add <repo-name> https://helm.redis.io/
+   ```
 
 2. Install the Helm chart into a new namespace.
 
 ```sh
-helm install <release-name> redis/redis-enterprise-operator \
+helm install <release-name> <repo-name>/redis-enterprise-operator \
     --version <chart-version> \
     --namespace <namespace-name> \
     --create-namespace
@@ -70,12 +68,12 @@ To monitor the installation add the `--debug` flag. The installation runs severa
 
 ### Specify values during install
 
-1. View configurable values with `helm show values <repo-name>/<chart-name>`.
+1. View configurable values with `helm show values <repo-name>/redis-enterprise-operator`.
 
 2. Install the Helm chart, overriding specific value defaults using `--set`.
 
 ```sh
-helm install <operator-name> redis/redis-enterprise-operator \
+helm install <operator-name> <repo-name>/redis-enterprise-operator \
     --version <release-name> \
     --namespace <namespace-name> \
     --create-namespace
@@ -85,20 +83,44 @@ helm install <operator-name> redis/redis-enterprise-operator \
 
 ### Install with values file
 
-1. View configurable values with `helm show values <repo-name>/<chart-name>`.
+1. View configurable values with `helm show values <repo-name>/redis-enterprise-operator`.
 
 2. Create a YAML file to specify the values you want to configure.
 
 3. Install the chart with the `--values` option.
 
 ```sh
-helm install <operator-name> redis/redis-enterprise-operator \
+helm install <operator-name> <repo-name>/redis-enterprise-operator \
     --version <release-name> \
     --namespace <namespace-name> \
     --create-namespace \
     --values <path-to-values-file>
 ```
 
+## Migrate from a non-Helm installation
+
+To migrate an existing non-Helm installation of the Redis Enterprise operator to a Helm-based installation:
+
+1. [Upgrade]({{<relref "operate/kubernetes/upgrade">}}) your existing Redis Enterprise operator to match the version of the Helm chart you want to install. Use the same non-Helm method you used for the original installation.
+
+2. [Install](#install) the Helm chart adding the `--take-ownership` flag:
+
+   ```sh
+   helm install <release-name> <path-to-chart> --take-ownership
+   ```
+
+   - The `--take-ownership` flag is available with Helm versions 3.18 or later.
+   - This flag is only needed for the first installation of the chart. Subsequent upgrades don't require this flag.
+   - Use the `helm install` command, not `helm upgrade`.
+
+3. Delete the old `ValidatingWebhookConfiguration` object from the previous non-Helm installation:
+
+   ```sh
+   kubectl delete validatingwebhookconfiguration redis-enterprise-admission
+   ```
+
+   This step is only needed when the `admission.limitToNamespace` chart value is set to `true` (the default). In this case, the webhook object installed by the chart is named `redis-enterprise-admission-<namespace>`. If `admission.limitToNamespace` is set to `false`, the webhook installed by the chart is named `redis-enterprise-admission`, and the existing webhook object is reused.
+
 ## Upgrade the chart
 
 To upgrade an existing Helm chart installation:
@@ -116,7 +138,7 @@ helm upgrade my-redis-enterprise .
 You can also upgrade using the Redis Helm repository:
 
 ```sh
-helm upgrade <release-name> redis/redis-enterprise-operator --version <chart-version>
+helm upgrade <release-name> <repo-name>/redis-enterprise-operator --version <chart-version>
 ```
 
 To upgrade the chart on **OpenShift**, include the `openshift.mode=true` parameter:
@@ -149,6 +171,5 @@ This removes all Kubernetes resources associated with the chart and deletes the
 ## Known limitations
 
 - The steps for [creating the RedisEnterpriseCluster (REC)]({{<relref "operate/kubernetes/deployment/quick-start#create-a-redis-enterprise-cluster-rec">}}) and other custom resources remain the same.
-- Migrations are not supported.
 - The chart doesn't include configuration options for multiple namespaces, rack-awareness, and Vault integration. The steps for configuring these options remain the same.
 - The chart has had limited testing in advanced setups, including Active-Active configurations, air-gapped deployments, and IPv6/dual-stack environments.