spegel: EKS kubelet fail to start with latest 1.29 AMI - `amazon-eks-node-1.29-v20240129`

          Update for the thread, I've had kubelet fail to start with the above patch on the latest 1.29 AMI - `amazon-eks-node-1.29-v20240129`.

Not sure why yet just thought I’d raise it as commenting out the userData patch got the nodes up and running.

_Originally posted by @danielloader in https://github.com/XenitAB/spegel/issues/217#issuecomment-1926762308_

About this issue

  • Original URL
  • State: closed
  • Created 3 years ago
  • Comments: 15 (12 by maintainers)

Most upvoted comments

We had the same issue with 1.28. Had to comment out the userData

@phillebaba FWIW your solution works for me. I’m using EKS 1.29 with the amazon-eks-node-1.29-v20240307 AMI.

There is now a release containing the new option to override Containerd config. If someone has time to test and verify the new userdata script that would be great! I had a look at the old examples for user data and had a try to create something that I think would work.

#!/bin/bash
set -ex

mkdir -p /etc/containerd/config.d
cat > /etc/containerd/config.d/spegel.toml << EOL
[plugins."io.containerd.grpc.v1.cri".registry]
   config_path = "/etc/containerd/certs.d"
[plugins."io.containerd.grpc.v1.cri".containerd]
   discard_unpacked_layers = false
EOL

/etc/eks/bootstrap.sh

We can close this issue when the compatibility guide has been updated. https://github.com/XenitAB/spegel/blob/main/docs/COMPATIBILITY.md

Yes, possibly.

It’s Kubecon season so my free time is sparse this month. But I’ll get to it eventually.