-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Issues: awslabs/amazon-eks-ami
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Author
Label
Projects
Milestones
Assignee
Sort
Issues list
bug(containerd): 1.7.11 has memory leak for kubectl exec fixed in 1.7.21
bug
Something isn't working
#1999
opened Oct 8, 2024 by
robert-heinzmann-logmein
Check for ecr-fips endpoint availability - VPC Endpoint
bug
Something isn't working
#1984
opened Oct 1, 2024 by
jeremymcgee73
bug(nodeadm): containerd BaseRuntimeSpec config not merged correctly
#1928
opened Aug 19, 2024 by
vedantrathore
Nodeadm-run service fails if containerd is not fully initialized and running
#1917
opened Aug 10, 2024 by
ajvn
Build fails when passing AWS_ACCESS_KEY_ID because it assumes that key has access to bucket
#1772
opened Apr 25, 2024 by
mebays
Hardened Source Image throws:
cannot stat ‘/tmp/worker/configure-clocksource.service’: No such file or directory
#1765
opened Apr 16, 2024 by
mebays
EKS Worker AMI v20240315 or newer for EKS versions 1.23 or older now contains Docker v25 instead of v20
#1733
opened Mar 22, 2024 by
ptailor1193
AL2023 should use actual max pods to calculate kube-reserved
#1698
opened Mar 1, 2024 by
stevehipwell
Amazon Linux 2023 (AL2023) is now generally available for MNG, Karpenter, and self managed nodes
#1696
opened Feb 29, 2024 by
ptailor1193
Can eks bootstrap.sh support to fips and use fips aws endpoints
#1681
opened Feb 21, 2024 by
kalpanathanneeru21
SSM-Agent not using FIPS endpoints, on FIPS enabled EKS cluster
#1675
opened Feb 16, 2024 by
MikeL-sfdc
Previous Next
ProTip!
Exclude everything labeled
bug
with -label:bug.