-
### Description
**Observed Behavior**:
Instance takes more than 5 minutes to terminate. Not sure if this is a bug or to be expected, but this sounds quite long (especially since we run `SpotToSpotCo…
-
Checklist:
* [ ] I've searched in the docs and FAQ for my answer: https://bit.ly/argocd-faq.
* [ ] I've included steps to reproduce the bug.
* [ ] I've pasted the output of `argocd version`.
…
-
/kind flake
The Karpenter prow jobs are flaky because of Karpenter's aggressive node churn.
[This run](https://prow.k8s.io/view/gs/kubernetes-jenkins/logs/e2e-kops-aws-ipv6-karpenter/1729771066…
-
/kind feature
**1. Describe IN DETAIL the feature/behavior/change you would like to see.**
[Karpenter v0.32 was released](https://github.com/aws/karpenter/releases/tag/v0.32.0) with a v1beta1 that…
-
### Description
At the moment, the documentation at [Karpenter](https://karpenter.sh/v1.0/upgrading/compatibility/#security-patches) states:
> While we are in major version 0, we will not release …
-
### Description
**Observed Behavior**:
- Nodes are running and healthy
- Suddenly the pods of a node turn into Terminating state
- Validating the node is in NotReady state
- Description of the …
-
### Description
**Observed Behavior**:
Karpenter is always disrupting node via drift, even consolidate configuration is `expireAfter: Never` and `consolidateAfter: Never`.
This issue is happen afte…
-
### Description
**Observed Behavior**:
NodeClaims enter a Drifted state, but fail to become disrupted.
```
$ kubectl get nodeclaim worker-test-disruption-xz5jd -o yaml
apiVersion: karpenter.sh/v1…
-
### Description
**What problem are you trying to solve?**
Trying to understand the binpack overhead in the k8s cluster
**How important is this feature to you?**
Can be very useful in optimizin…
-
### Description
**Observed Behavior**:
Karpented scaled nodes as a result of KEDA/HPA commands. Finally it resulted in a single beefy with no load and throws this **Unconsolidatable** reason.
…