add VPA for ALBC and make memory configurable

Author: Martin Linkhorst

cluster/config-defaults.yaml

@@ -1290,3 +1290,6 @@ aws_vpc_cni_custom_networking: "false"
 aws_vpc_cni_enable_network_policy: "false"
 # specify the network policy enforcement mode.
 aws_vpc_cni_network_policy_enforcing_mode: "standard"
+
+# aws-load-balancer-controller resource settings
+aws_load_balancer_controller_mem: "200Mi"

cluster/manifests/aws-load-balancer-controller/deployment.yaml

@@ -46,10 +46,10 @@ spec:
         resources:
           limits:
             cpu: 100m
-            memory: 200Mi
+            memory: {{ .Cluster.ConfigItems.aws_load_balancer_controller_mem }}
           requests:
             cpu: 100m
-            memory: 200Mi
+            memory: {{ .Cluster.ConfigItems.aws_load_balancer_controller_mem }}
         securityContext:
           allowPrivilegeEscalation: false
           readOnlyRootFilesystem: true

cluster/manifests/aws-load-balancer-controller/vpa.yaml

@@ -0,0 +1,22 @@
+# {{- if eq .Cluster.Provider "zalando-eks"}}
+apiVersion: autoscaling.k8s.io/v1
+kind: VerticalPodAutoscaler
+metadata:
+  name: aws-load-balancer-controller
+  namespace: kube-system
+  labels:
+    application: kubernetes
+    component: aws-load-balancer-controller
+spec:
+  targetRef:
+    apiVersion: apps/v1
+    kind: Deployment
+    name: aws-load-balancer-controller
+  updatePolicy:
+    updateMode: Auto
+  resourcePolicy:
+    containerPolicies:
+    - containerName: controller
+      maxAllowed:
+        memory: {{ .Cluster.ConfigItems.aws_load_balancer_controller_mem }}
+# {{- end }}