-
Notifications
You must be signed in to change notification settings - Fork 240
Issues: kubernetes-sigs/karpenter
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
Label
Projects
Milestones
Assignee
Sort
Issues list
Option for KWOK additional Categorizes issue or PR as related to a new feature.
priority/important-soon
Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
triage/needs-information
Indicates an issue needs more information in order to work on it.
AllowUndefined
labels
kind/feature
#2045
opened Mar 3, 2025 by
alec-rabold
Karpenter should handle when it is creating nodes that aren't used
kind/feature
Categorizes issue or PR as related to a new feature.
priority/awaiting-more-evidence
Lowest priority. Possibly useful, but not yet enough support to actually get it done.
triage/needs-information
Indicates an issue needs more information in order to work on it.
#2043
opened Feb 28, 2025 by
GnatorX
NodeRepair respects PDBs / terminationGracePeriodSeconds when nodepool does not have terminationGracePeriod set
kind/bug
Categorizes issue or PR as related to a bug.
needs-priority
triage/needs-investigation
Issues that need to be investigated before triaging
#2042
opened Feb 28, 2025 by
andrewhibbert
DisruptionReason
status condition isn't propagated for forceful disruptions
good first issue
#2023
opened Feb 21, 2025 by
jonathan-innis
Add Denotes an issue ready for a new contributor, according to the "help wanted" guidelines.
help wanted
Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.
kind/feature
Categorizes issue or PR as related to a new feature.
priority/important-soon
Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
triage/accepted
Indicates an issue or PR is ready to be actively worked on.
karpenter_pods_drained_total
during Node drain
good first issue
#2021
opened Feb 21, 2025 by
jonathan-innis
Add Denotes an issue ready for a new contributor, according to the "help wanted" guidelines.
help wanted
Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.
kind/feature
Categorizes issue or PR as related to a new feature.
priority/important-soon
Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
triage/accepted
Indicates an issue or PR is ready to be actively worked on.
karpenter_pods_disrupted_total
when NodeClaims are disrupted
good first issue
#2020
opened Feb 21, 2025 by
jonathan-innis
Include Nodepool disruption budget information in the NodePool status
help wanted
Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.
kind/feature
Categorizes issue or PR as related to a new feature.
priority/important-longterm
Important over the long term, but may not be staffed and/or may need multiple releases to complete.
triage/accepted
Indicates an issue or PR is ready to be actively worked on.
#2017
opened Feb 20, 2025 by
cnmcavoy
Emit DisruptionBlocked events on affected pod or pdb resource
kind/feature
Categorizes issue or PR as related to a new feature.
priority/important-longterm
Important over the long term, but may not be staffed and/or may need multiple releases to complete.
triage/accepted
Indicates an issue or PR is ready to be actively worked on.
#2016
opened Feb 20, 2025 by
cnmcavoy
DaemonSet pods circle in FAILED state due to rescheduling to node which is terminated
kind/bug
Categorizes issue or PR as related to a bug.
priority/important-soon
Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
triage/needs-investigation
Issues that need to be investigated before triaging
#2009
opened Feb 19, 2025 by
StepanS-Enverus
Add OTEL Tracing to Scheduling/Consolidation
kind/feature
Categorizes issue or PR as related to a new feature.
priority/important-soon
Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
triage/accepted
Indicates an issue or PR is ready to be actively worked on.
#2005
opened Feb 18, 2025 by
jonathan-innis
marking consolidatable
log messages are duplicated due to read-after-write inconsistency
good first issue
#2002
opened Feb 17, 2025 by
jonathan-innis
Ensure we use Denotes an issue ready for a new contributor, according to the "help wanted" guidelines.
help wanted
Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.
kind/cleanup
Categorizes issue or PR as related to cleaning up code, process, or technical debt.
kind/feature
Categorizes issue or PR as related to a new feature.
triage/accepted
Indicates an issue or PR is ready to be actively worked on.
Name()
consistently in our Reconcilers
good first issue
#2001
opened Feb 17, 2025 by
jonathan-innis
Host KWOK provider images in public ECR
kind/feature
Categorizes issue or PR as related to a new feature.
priority/important-longterm
Important over the long term, but may not be staffed and/or may need multiple releases to complete.
triage/accepted
Indicates an issue or PR is ready to be actively worked on.
#1997
opened Feb 16, 2025 by
alec-rabold
karpenter_scheduler_unfinished_work_seconds
is not registered with the Prometheus Registry
good first issue
#1994
opened Feb 14, 2025 by
jonathan-innis
karpenter_scheduler_unschedulable_pods_count
has unnecessary DeletePartialMatch
in the scheduler
good first issue
#1993
opened Feb 14, 2025 by
jonathan-innis
Dynamically set Disk Volume size.
kind/feature
Categorizes issue or PR as related to a new feature.
priority/backlog
Higher priority than priority/awaiting-more-evidence.
triage/accepted
Indicates an issue or PR is ready to be actively worked on.
#1988
opened Feb 13, 2025 by
gurpalw
Ungraceful pod termination
kind/bug
Categorizes issue or PR as related to a bug.
triage/needs-information
Indicates an issue needs more information in order to work on it.
#1987
opened Feb 13, 2025 by
aquam8
an expected drift by Categorizes issue or PR as related to a bug.
triage/needs-information
Indicates an issue needs more information in order to work on it.
scheduling.areRequirementsDrifted
has not happened when adding a new requirements field.
kind/bug
#1974
opened Feb 7, 2025 by
flavono123
Not able to proceed consolidation on big cluster
performance
Issues relating to performance (memory usage, cpu usage, timing)
priority/important-longterm
Important over the long term, but may not be staffed and/or may need multiple releases to complete.
triage/accepted
Indicates an issue or PR is ready to be actively worked on.
#1970
opened Feb 6, 2025 by
Hawksbk
Pod events controllers should use PodScheduled's Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.
kind/cleanup
Categorizes issue or PR as related to cleaning up code, process, or technical debt.
performance
Issues relating to performance (memory usage, cpu usage, timing)
priority/important-soon
Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
triage/accepted
Indicates an issue or PR is ready to be actively worked on.
lastTransitionTime
to mark when pod events occur
help wanted
#1965
opened Feb 5, 2025 by
jonathan-innis
Consolidation does not happen even when there is cheaper combination of instances available
consolidation
kind/feature
Categorizes issue or PR as related to a new feature.
performance
Issues relating to performance (memory usage, cpu usage, timing)
priority/important-longterm
Important over the long term, but may not be staffed and/or may need multiple releases to complete.
triage/accepted
Indicates an issue or PR is ready to be actively worked on.
#1962
opened Feb 5, 2025 by
codeeong
Ensure pods that can't drain aren't considered for provisioning rescheduling
kind/feature
Categorizes issue or PR as related to a new feature.
triage/accepted
Indicates an issue or PR is ready to be actively worked on.
#1928
opened Jan 24, 2025 by
jorgeperezc
Support ignoring specific pods when calculating consolidateAfter
consolidation
kind/feature
Categorizes issue or PR as related to a new feature.
priority/awaiting-more-evidence
Lowest priority. Possibly useful, but not yet enough support to actually get it done.
triage/accepted
Indicates an issue or PR is ready to be actively worked on.
#1921
opened Jan 16, 2025 by
rkilingr
Karpenter runtime logs showing tons of record: incompatible with nodepool , daemonset overhead
kind/bug
Categorizes issue or PR as related to a bug.
needs-triage
Indicates an issue or PR lacks a `triage/foo` label and requires one.
#1904
opened Jan 7, 2025 by
wangsic
Disruption budgets pertaining to node labels
kind/feature
Categorizes issue or PR as related to a new feature.
triage/accepted
Indicates an issue or PR is ready to be actively worked on.
#1902
opened Jan 6, 2025 by
tobbbles
Previous Next
ProTip!
What’s not been updated in a month: updated:<2025-02-06.