Skip to content

Issues: aws/karpenter-provider-aws

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
Filter by author
Loading
Label
Filter by label
Loading
Use alt + click/return to exclude labels
or + click/return for logical OR
Projects
Filter by project
Loading
Milestones
Filter by milestone
Loading
Assignee
Filter by who’s assigned
Sort

Issues list

Unable to set Flex instance-family as priority and default instance-families as fallback. lifecycle/stale question Issues that are support related questions triage/needs-information Marks that the issue still needs more information to properly triage
#7751 opened Feb 17, 2025 by asamudrala1
nodeclaim failing, node is created but not added to the cluster bug Something isn't working lifecycle/stale triage/needs-information Marks that the issue still needs more information to properly triage
#7738 opened Feb 14, 2025 by sambordoloi
karpenter Failed to schedule pod when using topology.kubernetes.io/zone, it doesn't create node bug Something isn't working lifecycle/stale triage/needs-information Marks that the issue still needs more information to properly triage
#7713 opened Feb 8, 2025 by ziyi-bear
panic: storage is (re)initializing bug Something isn't working lifecycle/stale triage/needs-information Marks that the issue still needs more information to properly triage
#7709 opened Feb 7, 2025 by mcleantom
Latest Karpenter versions not useable when traversing AWS Network Firewall bug Something isn't working lifecycle/stale triage/needs-information Marks that the issue still needs more information to properly triage
#7617 opened Jan 21, 2025 by firke
Karpenter 1.0.6 - failed to assign an IP address to container bug Something isn't working lifecycle/stale triage/needs-information Marks that the issue still needs more information to properly triage
#7318 opened Nov 4, 2024 by genseb13011
karpenter pods CrashLoopBackOff - Readiness probe failed read: connection reset by peer / Liveness probe failed connect: connection refused bug Something isn't working lifecycle/stale triage/solved Mark the issue as solved by a Karpenter maintainer. This gives time for the issue author to confirm.
#7256 opened Oct 20, 2024 by iamsaurabhgupt
TLS Error with Karpenter Liveness and Readiness Probes: remote error: tls: unrecognized name bug Something isn't working lifecycle/stale triage/needs-information Marks that the issue still needs more information to properly triage
#7027 opened Sep 17, 2024 by oluranticode
Support cordon-only mode on spot interruption for cost efficiency feature New feature or request lifecycle/stale triage/needs-information Marks that the issue still needs more information to properly triage
#7024 opened Sep 17, 2024 by int128
ProTip! Mix and match filters to narrow down what you’re looking for.