From cc17998ff75411100f1d5db036bf65ad1d6e24f6 Mon Sep 17 00:00:00 2001 From: Dave Protasowski Date: Fri, 10 Apr 2020 09:57:05 -0400 Subject: [PATCH] Upgrade documentation includes notes about storage version migration (#2369) * include notes when upgrading about the storage version migration k8s job * typos and white space * Update upgrade-installation.md Use artifact helper * Update docs/install/upgrade-installation.md Co-Authored-By: Matt Moore Co-authored-by: Matt Moore --- docs/install/upgrade-installation.md | 18 +++++++++++++++++- 1 file changed, 17 insertions(+), 1 deletion(-) diff --git a/docs/install/upgrade-installation.md b/docs/install/upgrade-installation.md index 7043b1fba..850165d99 100644 --- a/docs/install/upgrade-installation.md +++ b/docs/install/upgrade-installation.md @@ -59,6 +59,23 @@ If you have a plug-in installed, make sure to upgrade it at the same time as you upgrade your Knative components. For example, if you have the monitoring plug-in installed, upgrade it alongside Knative Serving and Eventing. + +### Upgrade existing resources to the latest stored version + +Our custom resources are stored within Kubernetes at a particular version. +As we introduce newer and remove older versions you'll need to migrate our resources +to the designated stored version. This ensures removing older versions +will succeed when upgrading. + +For the various subprojects - we have a K8s job to help operators perform this migration. +The release notes for each release will explicitly whether a migration is required. + +ie. +```bash +kubectl apply --filename {{< artifact repo="serving" file="serving-storage-version-migration.yaml" >}} +``` + + ## Performing the upgrade To upgrade, apply the `.yaml` files for the subsequent minor versions of all @@ -138,4 +155,3 @@ for the old pods as they are cleaned up. If necessary, repeat the upgrade process until you reach your desired minor version number. -