Add override for default target for autoscaler

The target as per the docs, when no label is set was 50.

This is still the case, however, it can be customised via
autoscaler.defaultTarget for people who are upgrading an old
cluster, or who deploy functions via REST and cannot yet
update their tooling

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.98
+version: 14.2.99
 sources:
 - https://github.com/openfaas/faas
 - https://github.com/openfaas/faas-netes

chart/openfaas/templates/autoscaler-dep.yaml

@@ -58,6 +58,11 @@ spec:
           value: "true"
         {{- end }}
 
+        {{- if .Values.autoscaler.defaultTarget }}
+        - name: default_target
+          value: {{ .Values.autoscaler.defaultTarget | quote }}
+        {{- end }}
+
         {{- if .Values.securityContext }}
         securityContext:
           {{- toYaml .Values.securityContext | nindent 10 }}

chart/openfaas/values.yaml

@@ -287,7 +287,10 @@ 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.16
+  image: ghcr.io/openfaasltd/autoscaler:0.3.17
+
+  # Default value for "com.openfaas.scale.target" when not set via label
+  defaultTarget: 50
 
   # replicas should only ever be set to 1, as a singleton.
   replicas: 1
@@ -418,7 +421,7 @@ nats:
 
 ## alertmanager is only used for OpenFaaS CE
 alertmanager:
-  image: prom/alertmanager:v0.28.0
+  image: prom/alertmanager:v0.28.1
   create: true
   resources:
     requests: