Merge pull request #243 from SgtCoDFish/update-images

Update other images, add release note section

Author: cert-manager-prow[bot]

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:
@@ -16,23 +36,27 @@ The release process for this repo is documented below:
    git tag --annotate --message="Release ${VERSION}" "${VERSION}"
    git push origin "${VERSION}"
    ```
+
 2. A GitHub action will see the new tag and do the following:
     - Build and publish any container images
     - Build and publish the Helm chart
     - Create a draft GitHub release
+
 3. Wait for the PR to be merged and wait for OCI Helm chart to propagate and become available from https://charts.jetstack.io (this might take a few hours).
+
 4. Visit the [releases page], edit the draft release, click "Generate release notes", then edit the notes to add the following to the top
     ```
     csi-driver-spiffe is a clean and simple way to get SPIFFE IDs for your Kubernetes pods with minimal dependencies and minimal fuss.
     ```
+
 5. Publish the release.
 
 ## Artifacts
 
 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-spiffe/actions/workflows/release.yaml
-[releases page]: https://github.com/cert-manager/csi-driver-spiffe/releases
+[releases page]: https://github.com/cert-manager/csi-driver-spiffe/releases

deploy/charts/csi-driver-spiffe/README.md

@@ -256,7 +256,7 @@ Target image repository.
 #### **app.driver.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.
@@ -297,7 +297,7 @@ Target image repository.
 #### **app.driver.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-spiffe/values.schema.json

@@ -312,7 +312,7 @@
       "type": "string"
     },
     "helm-values.app.driver.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"
     },
@@ -356,7 +356,7 @@
       "type": "string"
     },
     "helm-values.app.driver.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-spiffe/values.yaml

@@ -130,7 +130,7 @@ app:
       # 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:
@@ -155,7 +155,7 @@ app:
       # 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:
@@ -282,4 +282,4 @@ openshift:
     # +docs:type=boolean,string,null
     enabled: detect
     # Name of the SecurityContextConstraints to create RBAC for.
-    name: privileged
+    name: privileged