diff options
Diffstat (limited to 'doc/user/infrastructure/clusters/manage/management_project_applications/certmanager.md')
| -rw-r--r-- | doc/user/infrastructure/clusters/manage/management_project_applications/certmanager.md | 47 |
1 files changed, 16 insertions, 31 deletions
diff --git a/doc/user/infrastructure/clusters/manage/management_project_applications/certmanager.md b/doc/user/infrastructure/clusters/manage/management_project_applications/certmanager.md index 12f99af8d8d..58de5f5e368 100644 --- a/doc/user/infrastructure/clusters/manage/management_project_applications/certmanager.md +++ b/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. |