The pods in the systemd-logs daemonset are routinely consuming >2GB RAM. On small nodes (4GB RAM), especially control plane nodes, this can cause real issues with stability of the cluster.
Is this expected behaviour or is it possible there is a leak somewhere?
$ sonobuoy version --kubeconfig kubeconfig.yaml
Sonobuoy Version: v0.56.17
MinimumKubeVersion: 1.17.0
MaximumKubeVersion: 1.99.99
GitSHA:
GoVersion: go1.20.5
Platform: darwin/arm64
API Version: v1.27.3
The pods in the systemd-logs daemonset are routinely consuming >2GB RAM. On small nodes (4GB RAM), especially control plane nodes, this can cause real issues with stability of the cluster.
Is this expected behaviour or is it possible there is a leak somewhere?