Add more information regarding updating ods-pipeline

Author: Michael Sauter

README.md

@@ -23,10 +23,10 @@ The documentation provided by ODS pipeline has three audiences:
 * **Developers** contribute to the ODS pipeline project itself, for example by improving existing tasks, adding new ones, updating documentation, etc.
 
 **Admin Guide**
-* [Installation](/docs/admin-installation.adoc)
+* [Installation & Updating](/docs/admin-installation.adoc)
 
 **User Guide**
-* [Installation](/docs/user-installation.adoc)
+* [Installation & Updating](/docs/user-installation.adoc)
 * [ODS configuration](/docs/ods-configuration.adoc)
 * [Task Reference](/docs/tasks)
 * [Working with secrets in Helm](/docs/helm-secrets.adoc)

docs/admin-installation.adoc

@@ -1,4 +1,5 @@
 # Admin Installation Guide
+:toc:
 
 This guide will show how to install `ods-pipeline` in an existing ODS cluster. Note this is a one-time installation done by a cluster admin and does not need to be repeated for every project that wants to use `ods-pipeline`.
 
@@ -57,3 +58,7 @@ git subtree split --squash --prefix=deploy/central -b subtree-split-branch-$pipe
 git checkout -
 git subtree merge --prefix=ods-pipeline subtree-split-branch-$pipelineGitRef --squash
 ```
+
+Then you can update the `images` chart via `./install.sh -n ods --chart=images --values=values.images.ods.yaml,secrets.images.ods.yaml`. You may also use `--dry-run` to see the changes first. This will install `BuildConfig` and `ImageStream` resources in the `ods` namespace.
+
+In the same way, you can update the `tasks` chart via `./install.sh -n ods --chart=tasks --values=values.tasks.ods.yaml`. You may also use `--dry-run` to see the changes first. This will install the ODS tasks in cluster scope.

docs/user-installation.adoc

@@ -1,4 +1,5 @@
 # User Installation Guide
+:toc:
 
 This guide will show how to install `ods-pipeline` in an existing ODS project. It is possible to use the new Tekton pipelines approach and the classic Jenkins approach side by side.
 
@@ -56,3 +57,5 @@ git subtree split --squash --prefix=deploy/cd-namespace -b subtree-split-branch-
 git checkout -
 git subtree merge --prefix=ods-pipeline subtree-split-branch-$pipelineGitRef --squash
 ```
+
+Then you can update the resources via `./install.sh -n foo-cd -f values.foo-cd.yaml,secrets.foo-cd.yaml`. You may also use `--dry-run` to see the changes first.