From 5a38a038a10165332ed91bf9654ecc01cfda5133 Mon Sep 17 00:00:00 2001 From: Stefan Reimer Date: Sun, 4 Apr 2021 16:52:18 +0200 Subject: [PATCH] fix: use evictionHard to reserve node memory to avoid systemd mess --- charts/kubeadm/templates/KubeletConfiguration.yaml | 11 +++++++---- 1 file changed, 7 insertions(+), 4 deletions(-) diff --git a/charts/kubeadm/templates/KubeletConfiguration.yaml b/charts/kubeadm/templates/KubeletConfiguration.yaml index 2b0522e..d26567c 100644 --- a/charts/kubeadm/templates/KubeletConfiguration.yaml +++ b/charts/kubeadm/templates/KubeletConfiguration.yaml @@ -20,13 +20,16 @@ tlsCipherSuites: [TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_RSA_WITH_AES featureGates: {{ include "kubeadm.featuregates" ( dict "return" "map" "platform" .Values.platform ) }} # Minimal unit is 50m per pod podsPerCore: 20 +# cpuCFSQuotaPeriod: 10ms # Basic OS on Ubuntu 20.04 incl. crio -systemReserved: - memory: 256Mi +#systemReserved: +# memory: 256Mi # This should be dynamic based on number of maxpods and available cores # https://cloud.google.com/kubernetes-engine/docs/concepts/cluster-architecture#memory_cpu # Below are default minimal for 2 cores and minimum kubelet kubeReserved: cpu: 70m - memory: 128Mi -# cpuCFSQuotaPeriod: 10ms +# memory: 128Mi +# Lets use below to reserve memory for system processes as kubeReserved/sytemReserved doesnt go well with systemd it seems +evictionHard: + memory.available: "484Mi"