From 2410c9ab11729e58efe1d4e9e8c9432b2e4abff3 Mon Sep 17 00:00:00 2001 From: Jackson West Date: Sat, 6 May 2023 14:08:17 -0500 Subject: [PATCH 30/34] Patch haproxy maxconn value to avoid ulimit issue EKS-A uses haproxy 2.5 which errors if the maxconn value requires more FDs than allowed by the ulimit setting of docker. 100k maxconn is too high for the default ulimit on an al2 node. --- test/infrastructure/docker/internal/loadbalancer/config.go | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/test/infrastructure/docker/internal/loadbalancer/config.go b/test/infrastructure/docker/internal/loadbalancer/config.go index 8d2f70a02..1c6e7a68e 100644 --- a/test/infrastructure/docker/internal/loadbalancer/config.go +++ b/test/infrastructure/docker/internal/loadbalancer/config.go @@ -36,9 +36,10 @@ global log /dev/log local0 log /dev/log local1 notice daemon - # limit memory usage to approximately 18 MB - # (see https://github.com/kubernetes-sigs/kind/pull/3115) - maxconn 100000 + # EKS-A Change to 10k instead of 100k to avoid needing to raise default + # ulimits on al2 nodes and 10k seems like a reasonable default for + # our use cases + maxconn 10000 resolvers docker nameserver dns 127.0.0.11:53 -- 2.40.0