You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The EKS version was upgraded, and all upgrades except vpc-cni were successful.
Why did I fail when I just followed the recommendations? I don't know why xtables-lock occurred.
All instances are AL2.
Environment:
Kubernetes version (use kubectl version): 1.28
CNI Version v1.18.0-eksbuild.1
OS (e.g: cat /etc/os-release): AL2
Kernel (e.g. uname -a): x
AMI: amazon-eks-node-1.28-v20240703
The text was updated successfully, but these errors were encountered:
yieon-lyon
changed the title
[EKS] upgrade to v1.18.2-eksbuild.1 failed by 1.28
[EKS] upgrade to v1.18.2-eksbuild.1 failed xtables-lock
Jul 23, 2024
yieon-lyon
changed the title
[EKS] upgrade to v1.18.2-eksbuild.1 failed xtables-lock
[EKS] upgrade to v1.18.2-eksbuild.1 failed by xtables-lock
Jul 23, 2024
This issue is now closed. Comments on closed issues are hard for our team to see.
If you need more assistance, please either tag a team member or open a new issue that references this one.
What happened:
The EKS version was upgraded, and all upgrades except vpc-cni were successful.
Why did I fail when I just followed the recommendations? I don't know why xtables-lock occurred.
All instances are AL2.
Environment:
kubectl version
): 1.28cat /etc/os-release
): AL2uname -a
): xThe text was updated successfully, but these errors were encountered: