Bump other images, add note to release process about checking them

RELEASE.md

@@ -8,6 +8,26 @@ The release schedule for this project is ad-hoc. Given the pre-1.0 status of the
 
 There is a semi-automated release process for this project. When you create a Git tag with a tagname that has a `v` prefix and push it to GitHub it will trigger the [release workflow].
 
+### Preparing for a Release
+
+**BEFORE** doing a release, check if the other images in the csi-driver Helm
+chart need to be updated.
+
+These are:
+
+- registry.k8s.io/sig-storage/livenessprobe (`.Values.livenessProbeImage.tag`)
+- registry.k8s.io/sig-storage/csi-node-driver-registrar (`.Values.nodeDriverRegistrarImage.tag`)
+
+The latest image can be checked using `crane`:
+
+```console
+$ crane ls registry.k8s.io/sig-storage/livenessprobe | sort -V
+
+$ crane ls registry.k8s.io/sig-storage/csi-node-driver-registrar | sort -V
+```
+
+### Doing a Release
+
 The release process for this repo is documented below:
 
 1. Create a tag for the new release:
@@ -31,8 +51,8 @@ The release process for this repo is documented below:
 
 This repo will produce the following artifacts each release. For documentation on how those artifacts are produced see the "Process" section.
 
-- *Container Images* - Container images for the are published to `quay.io/jetstack`. 
+- *Container Images* - Container images for the are published to `quay.io/jetstack`.
 - *Helm chart* - An official Helm chart is maintained within this repo and published to `quay.io/jetstack` and `charts.jetstack.io` on each release.
 
 [release workflow]: https://github.com/cert-manager/csi-driver/actions/workflows/release.yaml
-[releases page]: https://github.com/cert-manager/csi-driver/releases
+[releases page]: https://github.com/cert-manager/csi-driver/releases

deploy/charts/csi-driver/README.md

@@ -173,7 +173,7 @@ Target image repository.
 #### **nodeDriverRegistrarImage.tag** ~ `string`
 > Default value:
 > ```yaml
-> v2.12.0
+> v2.13.0
 > ```
 
 Override the image tag to deploy by setting this variable. If no value is set, the chart's appVersion is used.
@@ -214,7 +214,7 @@ Target image repository.
 #### **livenessProbeImage.tag** ~ `string`
 > Default value:
 > ```yaml
-> v2.12.0
+> v2.15.0
 > ```
 
 Override the image tag to deploy by setting this variable. If no value is set, the chart's appVersion is used.

deploy/charts/csi-driver/values.schema.json

@@ -236,7 +236,7 @@
       "type": "string"
     },
     "helm-values.livenessProbeImage.tag": {
-      "default": "v2.12.0",
+      "default": "v2.15.0",
       "description": "Override the image tag to deploy by setting this variable. If no value is set, the chart's appVersion is used.",
       "type": "string"
     },
@@ -382,7 +382,7 @@
       "type": "string"
     },
     "helm-values.nodeDriverRegistrarImage.tag": {
-      "default": "v2.12.0",
+      "default": "v2.13.0",
       "description": "Override the image tag to deploy by setting this variable. If no value is set, the chart's appVersion is used.",
       "type": "string"
     },

deploy/charts/csi-driver/values.yaml

@@ -97,7 +97,7 @@ nodeDriverRegistrarImage:
   # Override the image tag to deploy by setting this variable.
   # If no value is set, the chart's appVersion is used.
   # +docs:property
-  tag: v2.12.0
+  tag: v2.13.0
 
   # Target image digest. Override any tag, if set.
   # For example:
@@ -122,7 +122,7 @@ livenessProbeImage:
   # Override the image tag to deploy by setting this variable.
   # If no value is set, the chart's appVersion is used.
   # +docs:property
-  tag: v2.12.0
+  tag: v2.15.0
 
   # Target image digest. Override any tag, if set.
   # For example: