knative
/
docs
mirror of https://github.com/knative/docs.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

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 <mattmoor@vmware.com>

Co-authored-by: Matt Moore <mattmoor@vmware.com>
This commit is contained in:
Dave Protasowski 2020-04-10 09:57:05 -04:00 committed by GitHub
parent cfae9520b5
commit cc17998ff7
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 17 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

18
docs/install/upgrade-installation.md
View File

@ -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 you upgrade your Knative components. For example, if you have the
monitoring plug-in installed, upgrade it alongside Knative Serving and Eventing. 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 ## Performing the upgrade
To upgrade, apply the `.yaml` files for the subsequent minor versions of all 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 If necessary, repeat the upgrade process until you reach your desired minor
version number. version number.