Fix for autoscaler in default RPS mode

When the previous image 0.3.17 was deployed, if no autoscaling
settings were set, then RPS was taking over as designed. But
due to a bug, it was setting a scale target of 0 instead of
50, meaning any invoked function scaled immediately to
maximum replicas.

This issue was only present in 0.3.17 when a chart-level
override was introduced. The new image 0.3.18 fixes the issue.

Signed-off-by: Alex Ellis (OpenFaaS Ltd) <[email protected]>

Author: alexellis

chart/openfaas/Chart.yaml

@@ -2,7 +2,7 @@ apiVersion: v2
 type: application
 description: OpenFaaS - Serverless Functions Made Simple
 name: openfaas
-version: 14.2.102
+version: 14.2.103
 sources:
 - https://github.com/openfaas/faas
 - https://github.com/openfaas/faas-netes

chart/openfaas/values.yaml

@@ -287,7 +287,7 @@ queueWorker:
 ## Advanced auto-scaler for scaling functions on RPS, CPU and in-flight requests
 ## Includes: scale to zero
 autoscaler:
-  image: ghcr.io/openfaasltd/autoscaler:0.3.17
+  image: ghcr.io/openfaasltd/autoscaler:0.3.18
 
   # Default value for "com.openfaas.scale.target" when not set via label
   defaultTarget: 50
@@ -317,7 +317,7 @@ autoscaler:
 ## To use with port-forwarding, set publicURL to 
 ## http://127.0.0.1
 dashboard:
-  image: ghcr.io/openfaasltd/openfaas-dashboard:0.5.31
+  image: ghcr.io/openfaasltd/openfaas-dashboard:0.5.34
   publicURL: https://dashboard.example.com
   # Name of signing key secret for sessions.
   # Leave blank for development, see https://docs.openfaas.com/openfaas-pro/dashboard/ for production and staging.