Upgrade cron-connector to fix panic

A panic made the cron-connector crash if the gateway return an error or EOF during its invocation. With faasd, this meant the connector stayed in an exited state with Kubernetes, it would have restarted, however it's always better if there is no panic, and the code can recover gracefully. Signed-off-by: Alex Ellis (OpenFaaS Ltd) <[email protected]>
openfaas · Jan 21, 2025 · 15a18af · 15a18af
1 parent 645dbda
commit 15a18af
Show file tree

Hide file tree

Showing 2 changed files with 3 additions and 3 deletions.
diff --git a/chart/cron-connector/Chart.yaml b/chart/cron-connector/Chart.yaml
@@ -1,7 +1,7 @@
 apiVersion: v1
 description: Trigger OpenFaaS Functions with cron schedules
 name: cron-connector
-version: 0.6.11
+version: 0.6.12
 sources:
 - https://github.com/openfaas/cron-connector
 home: https://www.openfaas.com

diff --git a/chart/cron-connector/values.yaml b/chart/cron-connector/values.yaml
@@ -1,9 +1,9 @@
 openfaasPro: false
 
 pro:
-  image: ghcr.io/openfaasltd/cron-connector:0.2.8
+  image: ghcr.io/openfaasltd/cron-connector:0.2.9
 
-image: ghcr.io/openfaas/cron-connector:0.6.1
+image: ghcr.io/openfaas/cron-connector:0.7.0
 
 logs:
   # Log debug messages