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
What happened:
I've been creating EKS cluster's node group with no success because of aws-node CrashLoopBackOff on nodes. When i viewed the ipamd logs i saw something like the following:
Attach logs
What you expected to happen:
How to reproduce it (as minimally and precisely as possible):
Anything else we need to know?:
Environment:
Kubernetes version (use kubectl version): 1.30
CNI Version: v1.18.1-eksbuild.3
OS (e.g: cat /etc/os-release):
Kernel (e.g. uname -a):
The text was updated successfully, but these errors were encountered:
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:
I've been creating EKS cluster's node group with no success because of aws-node CrashLoopBackOff on nodes. When i viewed the ipamd logs i saw something like the following:
Attach logs
What you expected to happen:
How to reproduce it (as minimally and precisely as possible):
Anything else we need to know?:
Environment:
kubectl version
): 1.30cat /etc/os-release
):uname -a
):The text was updated successfully, but these errors were encountered: