sincecutoff.com
/v1/json /v1/md llms.txt

What changed in eksctl.

We scan this tool’s changelog a few times a day and keep the changes that would alter your agent’s next action: 5 since February 2026, each linked to its source.

YOUR MODEL or
INTRODUCED
5 CHANGES
LATEST 2026-10-02 · 1 TOOLS
OCT 022026
eksctl

eksctl cluster creation can place control plane ENIs only in private subnets

When creating a cluster whose control plane ENIs must use private subnets, set `vpc.controlPlaneOnPrivateSubnets: true` in the config and run `eksctl create cluster -f config.yaml`. Public subnets remain available for other cluster resources.

apiVersion: eksctl.io/v1alpha5 kind: ClusterConfig metadata: name: cluster region: us-west-2 availabilityZones: - us-west-2a - us-west-2b vpc: controlPlaneOnPrivateSubnets: true # Save as config.yaml, then run: eksctl create cluster -f config.yaml
evidence github.comscore 0.97open card ↗
OCT 022026
eksctl

eksctl nodegroup config supports connectionTracking timeouts

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: 432000
evidence github.comscore 0.96open card ↗
AUG 142026
eksctl

eksctl supports control plane component configuration

When creating an EKS cluster with selected control plane settings, set the corresponding optional component fields in the ClusterConfig file; omitted fields use EKS defaults. To update an existing cluster, set at least one component field and run the update command; only components present in the file are updated.

eksctl create cluster -f control-plane-component-config.yaml
evidence github.comscore 0.98open card ↗
FEB 142026
eksctl

eksctl create/update pod identity associations accept --policy

When creating or updating a pod identity association with an additional policy, pass it with `--policy` and disable session tags. The policy adds restrictions beyond the IAM policies attached to the role.

eksctl create podidentityassociation --cluster <cluster> --namespace <namespace> --service-account-name <service-account> --policy '<policy-document>' --disable-session-tags
evidence github.comscore 0.95open card ↗
FEB 062026
eksctl

eksctl create iamserviceaccount accepts wildcard subject patterns

When multiple service accounts share a naming pattern, run `eksctl create iamserviceaccount` with `--subject-pattern="app-*"`; this makes the trust policy use `StringLike`. Use the narrowest pattern needed, since `*` allows any service account in the namespace to assume the role.

eksctl create iamserviceaccount --cluster=<clusterName> --name=<serviceAccountName> --namespace=<serviceAccountNamespace> --attach-policy-arn=<policyARN> --subject-pattern="app-*"
evidence github.comscore 0.98open card ↗