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?** We currently run karpenter on fargate nodes. the helm install of karpenter does not complete on v1.0.0 since the post-install-hook does...

bug
triage/accepted

### Description **Observed Behavior**: The [v1.0.0](https://github.com/aws/karpenter-provider-aws/tree/v1.0.0/charts/karpenter/crds) helm chart is pointing to the `v1beta1` CRDs - causing Karpenter to fail to start up upon installation. The `kubernetes-crd` chart could be used...

bug
needs-triage

### Description **What problem are you trying to solve?** My CRDs as they are managed externally so I don't want or need the post install hook running. I'd like to...

feature
needs-triage

### Description **Observed Behavior**: Due to https://github.com/aws/karpenter-provider-aws/blob/a70356ac2224e93d09372994a790fbdcad9cbc0f/charts/karpenter/templates/post-install-hook.yaml#L15 in conjunction with this issue https://github.com/argoproj/argo-cd/issues/6880#issuecomment-2274495939 means the hook never syncs and installation via ArgoCD isn't possible. **Expected Behavior**: Chart syncs via ArgoCD...

bug
triage/accepted

### Description **Observed Behavior**: Karpenter does not scale nodes even when the ResourceQuota defined in a namespace has been fully utilized. This leads to pods remaining unscheduled due to lack...

bug
needs-triage

Fixes https://github.com/aws/karpenter-provider-aws/issues/6765 **Description** Added configuration option for the ttlSecondsAfterFinished field on the post install job so that Argo CD based installs can complete (as Argo CD needs to reap the...

Fixes #6649 **Description** add an option in the value file to set custom annotations specificly to tthe custom resource definitions so we can set in our use case the helm...

**Tell us about your request** I'd like Karpenter to work correctly when not using the EKS optimised AMI calculations for `--kube-reserved` (as already discussed in #1490). The current logic in...

feature

### Description **What problem are you trying to solve?** I'd like the ability to set a common kubelet configuration value for maxPods and kubeReserved.memory but would like to retain the...

feature
needs-triage

### Description **What problem are you trying to solve?** Hi, In our recent migration to Karpenter, we have observed that for our generic x86 nodepool we have, Karpenter prefers m5(a)...

feature
needs-triage