Add maxClientMemory to values.yaml

A customer asked for this setting due to high memory usage whilst streaming video. Signed-off-by: Alex Ellis (OpenFaaS Ltd) <alexellis2@gmail.com>
inlets · May 11, 2023 · fb1a2a0 · fb1a2a0
1 parent cb511e5
commit fb1a2a0
Show file tree

Hide file tree

Showing 5 changed files with 96 additions and 69 deletions.
diff --git a/chart/inlets-operator/Chart.yaml b/chart/inlets-operator/Chart.yaml
@@ -2,7 +2,7 @@ apiVersion: v1
 appVersion: "1.0"
 description: inlets-operator for Kubernetes
 name: inlets-operator
-version: 0.17.4
+version: 0.17.5
 keywords:
 - networking
 - loadbalancer

diff --git a/chart/inlets-operator/templates/deployment.yaml b/chart/inlets-operator/templates/deployment.yaml
@@ -59,6 +59,9 @@ spec:
         {{- if .Values.plan }}
         - "-plan={{.Values.plan}}"
         {{- end }}
+        {{- if .Values.maxClientMemory }}
+        - "-max-client-memory={{.Values.maxClientMemory}}"
+        {{- end }}
         resources:
           {{- toYaml .Values.resources | nindent 12 }}
         env:

diff --git a/chart/inlets-operator/values.yaml b/chart/inlets-operator/values.yaml
@@ -45,8 +45,8 @@ image: "ghcr.io/inlets/inlets-operator:0.17.2"
 pullPolicy: "IfNotPresent"
 
 # These should match
-inletsClientImage: "ghcr.io/inlets/inlets-pro:0.9.14"
-inletsRelease: "0.9.14"
+inletsClientImage: "ghcr.io/inlets/inlets-pro:0.9.19"
+inletsRelease: "0.9.19"
 
 nameOverride: ""
 fullnameOverride: ""
@@ -56,6 +56,9 @@ resources:
     cpu: 100m
     memory: 128Mi
 
+# Set a maximum memory limit for the inlets client Deployments
+maxClientMemory: 128Mi
+
 nodeSelector: {}
 tolerations: []
 affinity: {}