Merge pull request #4061 from replicatedhq/update-helmchart-cr-ec-v3

Update Helmchart cr docs for ec v3

Author: paigecalvert

docs/partials/helm/_helm-builder-requirements.mdx

@@ -1,5 +1,5 @@
 The `builder` key has the following requirements and recommendations:
-* Replicated recommends that you include only the minimum Helm values in the `builder` key that are required to template the Helm chart with the correct image tags.
-* Use only static, or _hardcoded_, values in the `builder` key. You cannot use template functions in the `builder` key because values in the `builder` key are not rendered in a customer environment.
-* Any `required` Helm values that need to be set to render the chart templates must have a value supplied in the `builder` key. For more information about the Helm `required` function, see [Using the 'required' function](https://helm.sh/docs/howto/charts_tips_and_tricks/#using-the-required-function) in the Helm documentation.
+* Replicated recommends that you include only the minimum Helm values in the `builder` key required to template the Helm chart with the correct image tags.
+* Use only static, or _hardcoded_, values in the `builder` key. You can't use template functions in the `builder` key because values in the `builder` key are not rendered in a customer environment.
+* Any `required` Helm values that need to be set to render the chart templates must have a value in the `builder` key. For more information about the Helm `required` function, see [Using the 'required' function](https://helm.sh/docs/howto/charts_tips_and_tricks/#using-the-required-function) in the Helm documentation.
 * Specify `kubeVersion` in the root Helm chart. The Vendor Portal renders Helm charts with the minimum Kubernetes minor version that satisfies the `kubeVersion` in the root Helm chart. For example, if the chart specifies `kubeVersion: >=1.24.1`, then it's rendered with Kubernetes 1.25.0. If this fails or if a `kubeVersion` is not specified in the root Helm chart, then the Vendor Portal attempts to render the chart with each supported minor version of Kubernetes up to the latest version.

docs/partials/helm/_helm-cr-builder-airgap-intro.mdx

@@ -1,13 +1,13 @@
 The `builder` key contains the minimum Helm values required so that the output of `helm template` exposes all container images needed to install the chart in an air-gapped environment.
 
-The Replicated Vendor Portal uses the Helm values that you provide in the `builder` key to run `helm template` on the chart, then parses the output to generate a list of required images for the chart. 
+The Replicated Vendor Portal uses the Helm values in the `builder` key to run `helm template` on the chart. It then parses the output to generate a list of required images. 
 
 The Vendor Portal then uses this list of images to do the following:
 * Create the Helm CLI air gap installation instructions that are automatically made available to customers in the [Enterprise Portal](/vendor/enterprise-portal-about) or Download Portal. 
 * Build the `.airgap` bundle for a release to support air gap installations with a Replicated installer (Embedded Cluster, KOTS, kURL).
 * Determine which images to scan and report on in the [Security Center (Alpha)](/vendor/security-center-about).
 
-The `builder` key is required to support the following installation types:
+You must configure the `builder` key to support the following installation types:
 
 * Air gap installations with a Replicated installer (Embedded Cluster, KOTS, kURL)
 * Air gap installations with the Helm CLI

docs/partials/helm/_helm-cr-builder-example.mdx

@@ -1,6 +1,7 @@
-Many applications have images that are included or excluded based on a given condition.
+Many applications include or exclude images based on a given condition.
 
-For example, a Helm chart might include a conditional PostgreSQL Deployment, as shown in the Helm template below:
+For example, a Helm chart might include a conditional PostgreSQL Deployment,
+as shown in the following Helm template:
 
 ```yaml
 {{- if .Values.postgresql.enabled }}
@@ -29,7 +30,8 @@ spec:
 {{- end }}
 ```
 
-To ensure that the `postgresql` image is included in the air gap bundle for the release, the `postgresql.enabled` value is added to the `builder` key of the HelmChart custom resource and is hardcoded to `true`:
+To include the `postgresql` image in the air gap bundle,
+add `postgresql.enabled` to the `builder` key of the HelmChart custom resource and set it to `true`:
 
 ```yaml
 apiVersion: kots.io/v1beta2

docs/partials/helm/_helm-cr-chart-name.mdx

@@ -1,5 +1,8 @@
-Specifies the release name to use when installing this instance of the Helm chart. Defaults to the chart name.
+Specifies the release name to use when installing this instance of the Helm chart.
+Defaults to the chart name.
 
-The release name must be unique across all charts deployed in the namespace. To deploy multiple instances of the same Helm chart in a release, you must add an additional HelmChart custom resource with a unique release name for each instance of the Helm chart.
+The release name must be unique across all charts deployed in the namespace.
+To deploy multiple instances of the same Helm chart in a release,
+add a separate HelmChart custom resource with a unique release name for each instance.
 
 Must be a valid Helm release name that matches regex `^[a-z0-9]([-a-z0-9]*[a-z0-9])?(\\.[a-z0-9]([-a-z0-9]*[a-z0-9])?)*$` and is no longer than 53 characters.

docs/partials/helm/_helm-cr-chart-release-name.mdx

@@ -1,2 +1,2 @@
 The `chart` key allows for a mapping between the data in this definition and the chart archive itself.
-More than one `kind: HelmChart` can reference a single chart archive, if different settings are needed.
+You can create multiple HelmChart resources that all reference a single chart archive.

docs/partials/helm/_helm-cr-chart-version.mdx

@@ -1,3 +1,4 @@
 When the installer processes your release, it excludes any Helm chart if the output of the `exclude` field is `true`.
 
-The `exclude` attribute can be parsed by template functions. See [About Replicated template functions](template-functions-about).
+Template functions can parse the `exclude` attribute.
+See [About Replicated template functions](template-functions-about).

docs/partials/helm/_helm-cr-chart.mdx

@@ -1,4 +1,11 @@
-The `namespace` key specifies an alternative namespace where Replicated KOTS installs the Helm chart. **Default:** The Helm chart is installed in the same namespace as the Admin Console. The `namespace` attribute can be parsed by template functions. For more information about template functions, see [About template function contexts](template-functions-about).
+The `namespace` key specifies an alternative namespace to install the Helm chart.
+By default, for Embedded Cluster v2 and KOTS existing cluster installations,
+KOTS installs the chart in the same namespace as the Admin Console.
+For Embedded Cluster v3 installations, Embedded Cluster installs the chart in a namespace named `<your-app-slug>` by default.
 
+Template functions can parse the `namespace` attribute.
+For more information about template functions, see [About Replicated template functions](/reference/template-functions-about).
 
-If you specify a namespace in the HelmChart `namespace` field, you must also include the same namespace in the `additionalNamespaces` field of the Application custom resource manifest file. KOTS creates the namespaces listed in the `additionalNamespaces` field during installation. For more information, see [additionalNamespaces](custom-resource-application#additionalnamespaces) in the _Application_ reference.
+For Embedded Cluster v2 and KOTS existing cluster installations,
+if you specify a namespace in the HelmChart `namespace` field,
+you must also include the same namespace in the [additionalNamespaces](custom-resource-application#additionalnamespaces) field of the Application custom resource.