release: prepare for upgrade

Signed-off-by: Anthony Whalley <[email protected]>

Author: No9

Cargo.lock

@@ -18,6 +18,9 @@
 
 ## How should I integrate my own uploader?
 
+**This custom upload scenario is being replaced by the event pattern implemented in v8.9.0.**
+**More documentation will follow as a client is implemented**
+
 The core dump handler is designed to quickly move the cores *"off-box"* to an object storage environment with as much additional runtime information as possible.
 In order to provide the following benefits:
 
@@ -27,7 +30,7 @@ In order to provide the following benefits:
 
 - As Object Storage APIs have migrated to S3 as a defacto standard post processing services for scrubbers and indexing the data are easier to implement.
 
-It's strongly recommened that you maintain the upload pattern of moving the cores off the machine but you may wish to move them to a none S3 compabible host.
+It's strongly recommended that you maintain the upload pattern of moving the cores off the machine but you may wish to move them to a none S3 compabible host.
 
 This scenario is possible but the following aspects need consideration:
 

FAQ.md

@@ -10,9 +10,9 @@ sources:
 
 type: application
 
-version: v8.9.0
+version: v8.10.0
 
-appVersion: "v8.9.0"
+appVersion: "v8.10.0"
 
 icon: https://raw.githubusercontent.com/No9/core-dump-handler/master/assets/handle-with-care-svgrepo-com.svg
 
@@ -29,21 +29,26 @@ maintainers:
 
 annotations:
   artifacthub.io/changes: |
-    - kind: added
-      description:  Experimental event file creation
+    - kind: fixed
+      description:  Fix event sourcing setup in chart templates
       links:
         - name: GitHub PR
-          url: https://github.com/IBM/core-dump-handler/pull/122
+          url: https://github.com/IBM/core-dump-handler/pull/127
     - kind: fixed
-      description: Scheduler crashing due to updated depenendency
+      description: Downgrade to 0.31.0
       links:
         - name: GitHub Issue
-          url: https://github.com/IBM/core-dump-handler/issues/120
+          url: https://github.com/IBM/core-dump-handler/issues/126
+        - name: GitHub PR
+          url: https://github.com/IBM/core-dump-handler/pull/128
+    - kind: fixed
+      description:  Handle pullSecrets inside daemonset.yaml
+      links:
         - name: GitHub PR
-          url: https://github.com/IBM/core-dump-handler/pull/121
+          url: https://github.com/IBM/core-dump-handler/pull/130
   artifacthub.io/images: |
     - name: core-dump-handler
-      image: quay.io/icdh/core-dump-handler:v8.9.0
+      image: quay.io/icdh/core-dump-handler:v8.10.0
   artifacthub.io/license: MIT
   artifacthub.io/signKey: |
     fingerprint: BED079E67FD431E45301B1C9949E671B46AC8A34

charts/core-dump-handler/Chart.yaml

@@ -3,7 +3,7 @@ replicaCount: 1
 image:
   registry: quay.io
   repository: icdh/core-dump-handler
-  tag: agent-s3-down
+  tag: pre-8.10.0
   pullPolicy: Always
   pullSecrets: []
   request_mem: "64Mi"