Comments (2)
jmdeal
commented on July 21, 2024
1
I think this is largely a consequence of our release notes being split between two repositories: the upstream library (kubernetes-sigs/karpenter) and the AWS provider (this repo). These release versions are currently coupled, so to get a full picture you'd want to check out the releases in both versions. For example, in the upstream v0.34.0 release disruption budgets is listed as a feature.
It would be nice to have a unified changelog, since the provider is the product that users interact with at the end of the day. I think this is especially true as we move to decouple the library and provider release versions post v1.
from karpenter-provider-aws.
jcmcken
commented on July 21, 2024
Thanks, that makes a lot of sense. I didn't realize there was a separate repo.
from karpenter-provider-aws.
Related Issues (20)
- Migrating pods from One NodePool to Another HOT 1
- `make setup` has been deleted but still exists in the document
- GPU workload pod failed to schedule due to low-priority gpu placeholder daemonset HOT 2
- Allocatable memory less than actual memory during scheduling (trn1.32x) HOT 2
- Upgrade process for Karpenter HOT 1
- Support pod PID limits through NodePool spec.template.spec.kubelet
- EC2 capacity blocks for ML in Karpenter Nodepools
- Pods were CrashLoopBackOff in provisioned node by karpenter(rare occurrences)
- Get used AMI-Images by metrics
- EC2 Instances configuration messed up when spawned by Karpenter, they fail to register to the cluster
- Metric karpenter_interruption_received_messages(message_type="SpotInterruptionKind") is not accurate
- karpenter unable to spin up nodes for statefulset
- Manage CRDs with Kustomize
- Karpenter frequently pulls up nodes and pods cannot be scheduled HOT 1
- no service port 8443 found for service "karpenter" after migrating from cluster autoscaler HOT 1
- Option to disable setting default blockDeviceMappings HOT 1
- Resolving STS Credentials with I/O Timeout - use karpenter DNS and no CoreDNS?
- Karpenter metrics documentation should be improved
- Node Metrics included nodes not managed by Karpenter
- Distribute workloads across multiple Availability Zones to mitigate the risk of single-zone failure. HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from karpenter-provider-aws.