eksctl nodegroup config supports connectionTracking timeouts
Introduced 2026-10-02 · score 0.96
HOW TO USE IT
For nodegroups running long-lived, mostly idle connections, set at least one timeout in `connectionTracking`; omitted fields retain EC2’s instance-type default. Configure it in the nodegroup config when creating the nodegroup.
apiVersion: eksctl.io/v1alpha5
kind: ClusterConfig
metadata:
name: <cluster-name>
region: <region>
managedNodeGroups:
- name: <nodegroup-name>
instanceType: <nitro-instance-type>
connectionTracking:
tcpEstablishedTimeout: 432000WHY THIS HELPS
Configure EC2 connection tracking timeouts for nodegroups that run workloads with long-lived, mostly idle connections.
BEFORE THIS CHANGE
The release note says this support lets users configure the timeouts in native nodegroup config without resorting to a hand-written launch template.
REQUIREMENTS AND LIMITATIONS
- Version: v0.231.0
- connectionTracking: Optional nodegroup block for connection tracking timeouts; if present, at least one timeout must be set.
- tcpEstablishedTimeout: Idle TCP established-connection timeout, in seconds; allowed range 60–432000.
- udpStreamTimeout: Idle UDP stream timeout, in seconds, for flows with more than one request-response transaction; allowed range 60–180.
- udpTimeout: Idle UDP timeout, in seconds, for flows with one direction of traffic or at most one request-response transaction; allowed range 30–60.
- Prerequisite: Every instance type the nodegroup can launch must be Nitro-based.
- Prerequisite: For pod interfaces to inherit the primary interface settings, VPC CNI must be v1.21.2 or v1.22.1, or later in those release lines; older versions apply the timeouts to node traffic only.
- At least one timeout must be set.
- Supported ranges are tcpEstablishedTimeout 60–432000 seconds, udpStreamTimeout 60–180 seconds, and udpTimeout 30–60 seconds.
- Timeouts left unset keep EC2's default for the instance type.
FIRST-PARTY EVIDENCE
- https://github.com/eksctl-io/eksctl/releases/tag/v0.231.0
- https://github.com/eksctl-io/eksctl/pull/8872
- https://eksctl.io/usage/nodegroup-connection-tracking/
Check the installed version and the source before using it. Entry JSON