Helm 3 warning to 1.3.0 (#740)

(cherry picked from commit 61f8b94)

Co-authored-by: Nick Chase <nchase@earthlink.net>

Author: augustmckendrick

docs/admin/backup/customization.md

@@ -16,6 +16,9 @@ The [Velero helm chart](https://vmware-tanzu.github.io/helm-charts/) is supplied
     For example, this command installs {{{ docsVersionInfo.k0rdentName }}} via `helm install` with a configured plugin, `BackupStorageLocation`
     and propagated credentials:
 
+    > NOTE:
+    > Please use helm v3.
+
     ```shell
     helm install kcm {{{ extra.docsVersionInfo.ociRegistry }}} \
      --version <version> \

docs/admin/backup/restore.md

@@ -12,6 +12,9 @@ In the event of disaster, you can restore from a backup by doing the following:
    will be part of your restored cluster. You can remove these objects after installation, but you
    can also install {{{ docsVersionInfo.k0rdentName }}} without them in the first place:
 
+    > NOTE:
+    > Please use helm v3.
+
     ```bash
     helm install kcm {{{ extra.docsVersionInfo.ociRegistry }}} \
      --version <version> \

docs/admin/installation/install-k0rdent.md

@@ -4,6 +4,9 @@ This section assumes that you already have a kubernetes cluster installed. If yo
 
 The actual management cluster is a Kubernetes cluster with the {{{ docsVersionInfo.k0rdentName }}} application installed. The simplest way to install {{{ docsVersionInfo.k0rdentName }}} is through its Helm chart.  You can find the latest release [here]({{{ docsVersionInfo.k0rdentTagList }}}), and from there you can deploy the Helm chart, as in:
 
+> NOTE:
+> Please use helm v3.
+
 ```shell
 helm install kcm {{{ extra.docsVersionInfo.ociRegistry }}} --version {{{ extra.docsVersionInfo.k0rdentDotVersion }}} -n kcm-system --create-namespace
 ```
@@ -37,6 +40,9 @@ And of course when you need to clean up, you can use helm as well. Follow these
 
 3. Remove the kcm Helm release:
 
+    > NOTE:
+    > Please use helm v3.
+
     ```shell
     helm uninstall kcm -n kcm-system
     ```

docs/admin/kof/kof-install.md

@@ -98,6 +98,10 @@ apply these steps to enable the [Istio](https://istio.io/) service mesh:
     ```
 
 3. Install the `kof-istio` chart to the management cluster:
+
+    > NOTE:
+    > Please use helm v3.
+
     ```shell
     helm upgrade -i --reset-values --wait \
       --create-namespace -n istio-system kof-istio \
@@ -125,6 +129,10 @@ and [kof-operators](https://github.com/k0rdent/kof/blob/v{{{ extra.docsVersionIn
 and apply this example, or use it as a reference:
 
 1. Install `kof-operators` as required by `kof-mothership`:
+
+    > NOTE:
+    > Please use helm v3.
+
     ```shell
     helm upgrade -i --reset-values --wait \
       --create-namespace -n kof kof-operators \
@@ -214,6 +222,10 @@ and apply this example, or use it as a reference:
     ```
 
 6. Install `kof-mothership`:
+
+    > NOTE:
+    > Please use helm v3.
+
     ```shell
     helm upgrade -i --reset-values --wait -n kof kof-mothership \
       -f mothership-values.yaml \
@@ -248,6 +260,10 @@ and apply this example, or use it as a reference:
         you may set the OpenStack-specific values described in step 10 of the [Regional Cluster](#regional-cluster) section
         as a values file with `storage:` key passed to `kof-regional` chart here.
     * Install these charts into the management cluster with default or custom values:
+
+        > NOTE:
+        > Please use helm v3.
+
         ```shell
         helm upgrade -i --reset-values --wait -n kof kof-regional \
           oci://ghcr.io/k0rdent/kof/charts/kof-regional --version {{{ extra.docsVersionInfo.kofVersions.kofDotVersion }}}

docs/admin/kof/kof-maintainence.md

@@ -30,6 +30,9 @@ kubectl delete --wait --cascade=foreground -f regional-cluster.yaml
 
 To remove KOF from the management cluster:
 
+> NOTE:
+> Please use helm v3.
+
 ```shell
 helm uninstall --wait --cascade foreground -n istio-system kof-istio
 helm uninstall --wait --cascade foreground -n kof kof-child

docs/admin/kof/kof-storing.md

@@ -75,6 +75,10 @@ To apply this option:
     ```
 
 3. Install the `kof-storage` and `kof-collectors` charts to the management cluster:
+
+    > NOTE:
+    > Please use helm v3.
+
     ```shell
     helm upgrade -i --reset-values --wait -n kof kof-storage \
       -f storage-values.yaml \
@@ -178,6 +182,10 @@ To apply this option:
     ```
 
 2. Install the `kof-collectors` chart to the management cluster:
+
+    > NOTE:
+    > Please use helm v3.
+
     ```shell
     helm upgrade -i --reset-values --wait -n kof kof-collectors \
       -f collectors-values.yaml \
@@ -235,6 +243,10 @@ To apply this option:
     ```
 
 2. Install the `kof-collectors` chart to the management cluster:
+
+    > NOTE:
+    > Please use helm v3.
+
     ```shell
     helm upgrade -i --reset-values --wait -n kof kof-collectors \
       -f collectors-values.yaml \
@@ -319,6 +331,10 @@ For now, however, just for the sake of this demo, you can use the most straightf
     ```
 
 5. Install the `kof-collectors` chart to the management cluster:
+
+    > NOTE:
+    > Please use helm v3.
+
     ```shell
     helm upgrade -i --reset-values --wait -n kof kof-collectors \
       -f collectors-values.yaml \

docs/quickstarts/quickstart-1-mgmt-node-and-cluster.md

@@ -100,6 +100,9 @@ helm installed into /usr/local/bin/helm
 
 Now we'll install {{{ docsVersionInfo.k0rdentName }}} itself into the k0s management cluster:
 
+> NOTE:
+> Please use helm v3.
+
 ```shell
 helm install kcm {{{ extra.docsVersionInfo.ociRegistry }}} --version {{{ extra.docsVersionInfo.k0rdentDotVersion }}} -n kcm-system --create-namespace
 ```