2

I'm attempting to follow instructions for resolving a data congestion issue by enabling 2 unsafe sysctls for certain pods running in a Kubernetes cluster where the Pods are deployed by EKS. To do this, I must enable those parameters in the nodes running those pods. The following command is for enabling on a per-node basis:

kubelet --allowed-unsafe-sysctls \
  'net.unix.max_dgram_qlen,net.core.somaxconn'

However, the Nodes in the cluster I am working with are deployed by EKS. The EKS cluster was deployed by using the Amazon dashboard (Not a yaml config file/terraform/etc). I am not sure how to translate the above step to have all nodes in my cluster have those systcl enabled.

ALostBegginer
  • 41
  • 4
  • Have you seen this issue https://stackoverflow.com/questions/68138789/enable-unsafe-sysctls-on-a-cluster-managed-by-amazon-eks? – Jakub Siemaszko Jun 28 '21 at 15:15
  • That's a link to this question – ALostBegginer Jun 28 '21 at 22:23
  • Sorry for that, I must have pasted the wrong thing, I meant https://github.com/awslabs/amazon-eks-ami/issues/184 and also https://itnext.io/of-kubernetes-unsafe-sysctls-performance-optimization-on-eks-d36cc0e3e894. – Jakub Siemaszko Jun 29 '21 at 12:48
  • You need to use a custom bootstrap script in the launch template of your managed node group. I posted a more detailed answer in this question https://stackoverflow.com/a/70346926/908257 – b3n Dec 14 '21 at 10:00
  • Does this answer your question? [Fixing DataDog agent congestion issues in Amazon EKS cluster](https://stackoverflow.com/questions/68092279/fixing-datadog-agent-congestion-issues-in-amazon-eks-cluster) – b3n Dec 14 '21 at 10:02

0 Answers0