Kubernetes 1.35 silently breaks AL2 EKS nodes that lost patches in November(medium.com)
2 pointsby HeinanCA8 hours ago2 comments
  • znpy8 hours ago
    Too bad it’s behind a paywall
  • znpy7 hours ago
    I was able to read the link through a non-paywalled friend link (thank you HeinanCA).

    Ok so the issue was they were using Amazon Linux 2... Which in fairness has been practically deprecated for a while.

    I mean, it's essentially a RHEL7 with frankenstein-style patches all the way up (new kernels etc).

    I was interested in this article because i just deployed an eks 1.35 cluster last week and i have to upgrade a few more cluster, but thankfully i'm already on AL2023.

    • HeinanCA3 hours ago
      Glad you're already on AL2023 - that's exactly the right place to be for 1.35. On the "deprecated for a while" point — fair, but there's a difference between "deprecated" and "kubelet refuses to start." Teams have been running AL2 through multiple K8s versions without incident. The silent November AMI cutoff combined with the 1.35 hard failure is a step change, not a continuation of the same slow deprecation curve. A lot of teams that were comfortable coasting until June 30 just had their timeline moved up without a notification.