helm: allow to configure bpf-nat-global-max using Helm

Set the value to the current value of option.NATMapEntriesGlobalDefault

A successive PR will reduce it for #10056

Signed-off-by: Tobias Klauser <tklauser@distanz.ch>

install/kubernetes/cilium/charts/config/templates/configmap.yaml

@@ -136,6 +136,10 @@ data:
   bpf-ct-global-tcp-max: "{{ .Values.global.bpf.ctTcpMax }}"
   bpf-ct-global-any-max: "{{ .Values.global.bpf.ctAnyMax }}"
 
+  # bpf-nat-global-max specified the maximum number of entries in the BPF NAT
+  # table.
+  bpf-nat-global-max: "{{ .Values.global.bpf.natMax }}"
+
   # Pre-allocation of map entries allows per-packet latency to be reduced, at
   # the expense of up-front memory allocation for the entries in the maps. The
   # default value below will minimize memory usage in the default installation;

install/kubernetes/cilium/values.yaml

@@ -202,6 +202,9 @@ global:
     # tracking table
     ctAnyMax: 262144
 
+    # natMax is the maximum number of entries for the NAT table
+    natMax: 841429
+
     # montiorAggregation is the level of aggregation for datapath trace events
     monitorAggregation: medium
 

install/kubernetes/quick-install.yaml

@@ -75,6 +75,10 @@ data:
   bpf-ct-global-tcp-max: "524288"
   bpf-ct-global-any-max: "262144"
 
+  # bpf-nat-global-max specified the maximum number of entries in the BPF NAT
+  # table.
+  bpf-nat-global-max: "841429"
+
   # Pre-allocation of map entries allows per-packet latency to be reduced, at
   # the expense of up-front memory allocation for the entries in the maps. The
   # default value below will minimize memory usage in the default installation;