Jens-Uwe Walther

> OK just to make sure I understand, the permanent fix for this is in the backlog so we won't see it for a while, but if I manually update...

Amazon has just released EKS managed add-on EBS CSI "v1.11.2-eksbuild.1". The new default for tolerations of DaemonSet "ebs-csi-node" was changed according to the requests from customers and community to: ```yml...

> I don't see it in the AWS console, nor from the AWS CLI. > >  > >  I tested in in eu-west-1 (Dublin/Ieland) in the morning. Usually...

Out of curiosity: Is this an issue for ALB IP target mode as well?

> @youwalther65 Looking at your log, you'll notice that it doesn't give you an error that it couldn't connect to the containerd socket. That means it connected to the socket...

I just had to point crictl to the right socket using: ` export CONTAINER_RUNTIME_ENDPOINT=unix:///run/containerd/containerd.sock` then crictl image and other commands just work without using CONTAINERD_NAMESPACE env variable. Otherwise I 'll...

Any news here or roadmap progress? Thx.

This can be closed because this issue provides the answers needed and proposes to update documentation regarding this. [https://github.com/weaveworks/eksctl/issues/5420#issuecomment-1205159412](url)

I faced the same issue $ eksctl info eksctl version: 0.101.0 kubectl version: v1.23.5 OS: linux on AWS EKS 1.22

ok, so this extension of eksctl doesn't deliver what we hoped, right? But I run into another thing when trying to follow the docs not sure what I am doing...