karpenter-provider-aws icon indicating copy to clipboard operation
karpenter-provider-aws copied to clipboard

Karpenter is a Kubernetes Node Autoscaler built for flexibility, performance, and simplicity.

Results 220 karpenter-provider-aws issues
Sort by recently updated
recently updated
newest added

### Description **What problem are you trying to solve?** When a subnet is almost out of IPs, Karpenter will continue to launch nodes in it, leading to the VPC CNI...

feature

**Tell us about your request** Some fields in the EC2NodeClass spec (specifically the AWS Cloud Provider), are runtime defaulted, meaning that Karpenter assumes a default value at runtime. Some examples...

feature
v1.x

### Description **Observed Behavior**: This will be rather long as I describe the different scenarios we've tested. We have a deployment that, by default, does not specify `topologySpreadConstraints` or `affinity`...

bug
needs-triage

### Description **Observed Behavior**: Currently Karpenter recieves the account all the spot interruption and filters in the karpenter controller logic. But we have setup a lambda to filter the interruption...

bug
needs-triage

### Description **What problem are you trying to solve?** I have a generic `NodePool` that's used by a majority of my workloads, which has pretty lose requirements, except that it...

feature
needs-triage

### Description **Observed Behavior**: When a Fargate Profile is created for our `karpenter` namespace, the pods are restarted to move from the Managed Node Group to Fargate. However, they always...

bug
needs-triage

### Description **Observed Behavior**: When sudden load are input on deployment, pod got scaled up to 10 pods on new nodes and existing nodes but during downscaling of pods it...

question

### Description I created a new issue instead of Re-opening https://github.com/aws/karpenter-provider-aws/issues/6611 As I don't have a permission to re-open it. The reason I want to re-open it is documented in...

bug
needs-triage

### Description **How can the docs be improved?** For examples, the following metrics documentation should be improved. 1.karpenter_nodes_termination_time_seconds Examples ```shell karpenter_nodes_termination_time_seconds{app_kubernetes_io_instance="karpenter", app_kubernetes_io_managed_by="Helm", app_kubernetes_io_name="karpenter", app_kubernetes_io_version="0.36.0", helm_sh_chart="karpenter-0.36.0", instance="100.64.81.229:8000", job="kubernetes-service-endpoints", kubernetes_namespace="karpenter", nodepool="celeborn-worker-graviton", quantile="0.9",...

question
lifecycle/stale

### Description **Observed Behavior**: when changing instance-category, karpenter will spin up a node but delete the old new before the new node is ready. at times i've even seen it...

question
lifecycle/stale