Skip to content

Commit

Permalink
Adds a release note for upgrading legacy CRDs
Browse files Browse the repository at this point in the history
Signed-off-by: irbekrm <irbekrm@gmail.com>
  • Loading branch information
irbekrm authored and maelvls committed Jul 19, 2021
1 parent 82152ca commit 2fdc78c
Showing 1 changed file with 7 additions and 2 deletions.
9 changes: 7 additions & 2 deletions content/en/docs/installation/upgrading/upgrading-1.1-1.2.md
Original file line number Diff line number Diff line change
Expand Up @@ -7,8 +7,13 @@ type: "docs"

In an effort to introduce new features whilst keeping the project maintainable,
cert-manager now only supports Kubernetes down to version `v1.16`. This means
the `legacy` manifests have now been removed. You can read more
[here](/docs/installation/supported-releases/).
the `legacy` manifests have now been removed. Some users experience issues when
upgrading the legacy `CRD`s to `v1.2`. To solve this, you could replace the `CRD`s:
1. Backup `cert-manager` resources as described in [the docs](/docs/tutorials/backup/)
2. Run `kubectl replace -f https://github.com/jetstack/cert-manager/releases/download/v1.2.0/cert-manager.crds.yaml` to replace the CRDs.
3. Follow the standard upgrade process.
You can read more about supported Kubernetes versions
[here](/docs/installation/supported-releases/).

In this release some features have been deprecated. Please read the [version
1.2 release notes](../../../release-notes/release-notes-1.2/) for more details
Expand Down

0 comments on commit 2fdc78c

Please sign in to comment.