From 8c7fdac22d1fb0223f36037c0a1a326e0bc68196 Mon Sep 17 00:00:00 2001 From: JoshVanL Date: Fri, 16 Aug 2019 13:01:42 +0100 Subject: [PATCH 1/2] Adds documentation to describe how to perform 0.8->0.9 process Signed-off-by: JoshVanL --- docs/tasks/upgrading/upgrading-0.8-0.9.rst | 15 ++++++++++++++- 1 file changed, 14 insertions(+), 1 deletion(-) diff --git a/docs/tasks/upgrading/upgrading-0.8-0.9.rst b/docs/tasks/upgrading/upgrading-0.8-0.9.rst index 9404a17c8..77f5f0805 100644 --- a/docs/tasks/upgrading/upgrading-0.8-0.9.rst +++ b/docs/tasks/upgrading/upgrading-0.8-0.9.rst @@ -2,4 +2,17 @@ Upgrading from v0.8 to v0.9 =========================== -There are no special notes or considerations when upgrading from v0.8 to v0.9. +Due to a change in the API group that cert-manager deployments use +(`apps/v1beta1` to `apps/v1`), cert-manager deployments must first be deleted +before applying the new version. This will cause downtime until the new version +has been applied. To perform this action run: + +.. code-block:: shell + + kubectl delete deployments --namespace cert-manager \ + cert-manager \ + cert-manager-cainjector \ + cert-manager-webhook + +After this operation, follow the standard upgrade process as defined in the +:doc:`upgrade guide <./index>`. From f35afc216153ca3624c8235700d8bbd75b1b2730 Mon Sep 17 00:00:00 2001 From: JoshVanL Date: Fri, 16 Aug 2019 13:16:31 +0100 Subject: [PATCH 2/2] Add comment about backing up in 0.8 upgrade guide Signed-off-by: JoshVanL --- docs/tasks/upgrading/upgrading-0.8-0.9.rst | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/docs/tasks/upgrading/upgrading-0.8-0.9.rst b/docs/tasks/upgrading/upgrading-0.8-0.9.rst index 77f5f0805..57ef1e8fe 100644 --- a/docs/tasks/upgrading/upgrading-0.8-0.9.rst +++ b/docs/tasks/upgrading/upgrading-0.8-0.9.rst @@ -5,7 +5,9 @@ Upgrading from v0.8 to v0.9 Due to a change in the API group that cert-manager deployments use (`apps/v1beta1` to `apps/v1`), cert-manager deployments must first be deleted before applying the new version. This will cause downtime until the new version -has been applied. To perform this action run: +has been applied. No data loss will occur during this operation however it is +always advised to backup your data during an upgrade, which you can follow +:doc:`here <../backup-restore-crds>`. To perform this action run: .. code-block:: shell