Bump cluster management project template for 14.8

Cert-manager now defaults to 1.7.

Changelog: changed

doc/user/clusters/migrating_from_gma_to_project_template.md

@@ -69,9 +69,9 @@ See also [video walk-throughs](#video-walk-throughs) with examples.
 
     1. Copy the output of the following command (it might be big):
 
-   ```shell
-   helm get values runner -n gitlab-managed-apps -a --output yaml
-   ```
+        ```shell
+        helm get values runner -n gitlab-managed-apps -a --output yaml
+        ```
 
     1. Overwrite `applications/gitlab-runner/values.yaml` with the output of the previous command.
 
@@ -92,15 +92,18 @@ See also [video walk-throughs](#video-walk-throughs) with examples.
       chart version proposed in `applications/vault/values.yaml`.
 
     - Cert-manager:
-      - For users on Kubernetes version 1.20 or above, the deprecated cert-manager v0.10 is no longer valid and
-        and the upgrade includes a breaking change. So we suggest that you [backup and uninstall cert-manager v0.10](#backup-and-uninstall-cert-manager-v010)
-        , and install cert-manager v1.4 instead. To install this version, uncomment the `applications/cert-manager-1-4/helmfile.yaml`
-        from the [`./helmfile.yaml`](management_project_template.md#the-main-helmfileyml-file).
+      - For users on Kubernetes version 1.20 or above, the deprecated cert-manager v0.10 is no longer valid
+        and the upgrade includes a breaking change. So we suggest that you [backup and uninstall cert-manager v0.10](#backup-and-uninstall-cert-manager-v010),
+        and install the latest cert-manager instead. To install this version, uncomment `applications/cert-manager/helmfile.yaml`
+        from [`./helmfile.yaml`](management_project_template.md#the-main-helmfileyml-file).
         This triggers a pipeline to install the new version.
       - For users on Kubernetes versions lower than 1.20, you can stick to v0.10 by uncommenting
-        `applications/cert-manager/helmfile.yaml`
+        `applications/cert-manager-legacy/helmfile.yaml`
         in your project's main Helmfile ([`./helmfile.yaml`](management_project_template.md#the-main-helmfileyml-file)).
 
+        WARNING:
+        Cert-manager v0.10 breaks when Kubernetes is upgraded to version 1.20 or later.
+
 1. After following all the previous steps, [run a pipeline manually](../../ci/pipelines/index.md#run-a-pipeline-manually)
    and watch the `apply` job logs to see if any of your applications were successfully detected, installed, and whether they got any
    unexpected updates.

doc/user/infrastructure/clusters/manage/management_project_applications/certmanager.md

@@ -8,48 +8,33 @@ info: To determine the technical writer assigned to the Stage/Group associated w
 
 > - [Introduced](https://gitlab.com/gitlab-org/project-templates/cluster-management/-/merge_requests/5) in GitLab 14.0.
 > - Support for cert-manager v1.4 was [introduced](https://gitlab.com/gitlab-org/project-templates/cluster-management/-/merge_requests/69405) in GitLab 14.3.
+> - [Upgraded](https://gitlab.com/gitlab-org/project-templates/cluster-management/-/merge_requests/23) to cert-manager 1.7 in GitLab 14.8.
 
 Assuming you already have a [Cluster management project](../../../../../user/clusters/management_project.md) created from a
 [management project template](../../../../../user/clusters/management_project_template.md), to install cert-manager you should
 uncomment this line from your `helmfile.yaml`:
 
 ```yaml
-  - path: applications/cert-manager-1-4/helmfile.yaml
+  - path: applications/cert-manager/helmfile.yaml
 ```
 
 NOTE:
-We kept the `- path: applications/cert-manager/helmfile.yaml` with cert-manager v0.10 to facilitate
-the [migration from GitLab Managed Apps to a cluster management project](../../../../clusters/migrating_from_gma_to_project_template.md).
+If your Kubernetes version is earlier than 1.20 and you are [migrating from GitLab
+Managed Apps to a cluster management
+project](../../../../clusters/migrating_from_gma_to_project_template.md), then
+you can instead use `- path: applications/cert-manager-legacy/helmfile.yaml` to
+take over an existing release of cert-manager v0.10.
 
 cert-manager:
 
 - Is installed by default into the `gitlab-managed-apps` namespace of your cluster.
-- Can be installed with or without a default
-  [Let's Encrypt `ClusterIssuer`](https://cert-manager.io/docs/configuration/acme/), which requires an
-  email address to be specified. The email address is used by Let's Encrypt to
+- Includes a
+  [Let's Encrypt
+  `ClusterIssuer`](https://cert-manager.io/docs/configuration/acme/) enabled by
+  default. In the `certmanager-issuer` release, the issuer requires a valid email address
+  for `letsEncryptClusterIssuer.email`. Let's Encrypt uses this email address to
   contact you about expiring certificates and issues related to your account.
-
-To install cert-manager in your cluster, configure your `applications/cert-manager-1-4/helmfile.yaml` to:
-
-```yaml
-certManager:
-  installed: true
-  letsEncryptClusterIssuer:
-    installed: true
-    email: "user@example.com"
-```
-
-Or without the default `ClusterIssuer`:
-
-```yaml
-certManager:
-  installed: true
-  letsEncryptClusterIssuer:
-    installed: false
-```
-
-You can customize the installation of cert-manager by defining a
-`.gitlab/managed-apps/cert-manager/values.yaml` file in your cluster
-management project. Refer to the
-[chart](https://github.com/jetstack/cert-manager) for the
-available configuration options.
+- Can be customized in `applications/cert-manager/helmfile.yaml` by passing custom
+  `values` to the `certmanager` release. Refer to the
+  [chart](https://github.com/jetstack/cert-manager) for the available
+  configuration options.