Oleksii Kraievyi

Changing api version seems to be a step forward(in contrast to module version pin)

https://github.com/kubernetes/autoscaler/pull/6325 which is in 1.29.0 version should help. Cause https://docs.aws.amazon.com/eks/latest/userguide/pod-id-minimum-sdk.html

Now waiting for helm charts to catch up. :)

> @kappa8219, I have opened a PR #6475 for updating the helm chart. Thanks and I thumbed it up :)

> Just had this occur on one of our EKS 1.28 clusters, fixed it by: > > * Look at the node group node list to get current instance names...

> ~Can we get one for the `aws-ebs-csi-driver` too please 🙂 ?~

Found it :) https://github.com/kubernetes-sigs/aws-ebs-csi-driver/blob/86bde2066f5fb485b53606c286be15b9689ff025/charts/aws-ebs-csi-driver/values.yaml#L455C1-L456C17 Guys from AWS update documentation, please.

+1 with the same symptoms. ONLY with containers from images like this: ``` [root@ip-192-168-1-11 cdebug-0.0.8]# docker history 602401143452.dkr.ecr.us-east-1.amazonaws.com/eks/pause:3.5 IMAGE CREATED CREATED BY SIZE COMMENT 4643bd56bc8c 20 months ago ENTRYPOINT ["/pause"]...

Nope. Same thing. ``` [root@ip-192-168-1-239 cdebug-0.0.9]# ./cdebug exec -it --privileged 1d65808c0b32 Pulling debugger image... latest: Pulling from library/busybox 205dae5015e7: Pull complete Digest: sha256:7b3ccabffc97de872a30dfd234fd972a66d247c8cfc69b0550f276481852627c Status: Downloaded newer image for busybox:latest chroot:...

> @kappa8219 do you know what's the architecture of that `pause` image? Based on the busybox digest from the snippet above, you're on an `arm64` machine. But can it be...