-
Notifications
You must be signed in to change notification settings - Fork 233
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
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.
needs-priority
needs-triage
Indicates an issue or PR lacks a `triage/foo` label and requires one.
#2009
opened Feb 19, 2025 by
StepanS-Enverus
Allow platform agnostic e2e tests to ignore existing NodeClass and allow configurable e2e test timeout
kind/feature
Categorizes issue or PR as related to a new feature.
needs-priority
needs-triage
Indicates an issue or PR lacks a `triage/foo` label and requires one.
#2007
opened Feb 19, 2025 by
maxcao13
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
Feature NodeRepair not working
kind/bug
Categorizes issue or PR as related to a bug.
needs-priority
needs-triage
Indicates an issue or PR lacks a `triage/foo` label and requires one.
#2004
opened Feb 18, 2025 by
msvticket
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.
triage/accepted
Indicates an issue or PR is ready to be actively worked on.
#1997
opened Feb 16, 2025 by
alec-rabold
Too many pitfalls with V1 upgrade
kind/bug
Categorizes issue or PR as related to a bug.
triage/accepted
Indicates an issue or PR is ready to be actively worked on.
#1995
opened Feb 15, 2025 by
GnatorX
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
karpenter_ignored_pod_count
is not put under a subsystem
good first issue
#1992
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
Validate that the Conventional Commits standard is followed
good first issue
Denotes an issue ready for a new contributor, according to the "help wanted" guidelines.
kind/automation
Issues about the Karpenter's automation processes
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.
#1978
opened Feb 10, 2025 by
ellistarn
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/bug
Categorizes issue or PR as related to a bug.
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
Massive scaling and anomalous behaviors with the new forceful disruption method
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
Karpenter is not functioning as expected when used with reserved instances
kind/bug
Categorizes issue or PR as related to a bug.
triage/solved
Indicates an issue that has been considered solved by the maintainers.
#1926
opened Jan 23, 2025 by
paramjeet01
CronJobs in a namespace preventing consolidation
consolidation
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.
#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.
needs-triage
Indicates an issue or PR lacks a `triage/foo` label and requires one.
#1902
opened Jan 6, 2025 by
tobbbles
Karpenter is taking longer time to fallback to lower weighted nodepool when ICE errors are hit
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.
#1899
opened Jan 3, 2025 by
bparamjeet
Unexpected nodeclaim consolidation
triage/needs-information
Indicates an issue needs more information in order to work on it.
#1895
opened Dec 27, 2024 by
Lily922
Previous Next
ProTip!
no:milestone will show everything without a milestone.