tkestack/gpu-admission

Issues

• Why use Capacity instead of Allocatable?

  #22 opened 3 years ago by fighterhit
  1

• does not support kubernetes 1.23

  #24 opened 3 years ago by hwdef
  4

• I couldn't understand how to run scheduler.

  #7 opened 4 years ago by zewenli98
  7

• gpu-quota-admission pod running ,but 3456 connect: connection refused

  #26 opened a year ago by guoshengjer
  0

• why remove quota filter?

  #19 opened 2 years ago by hwdef
  0

• vgpu algorithm based on scheduler framework

  #17 opened 2 years ago by riverzhang
  0

• Why choose only one node?

  #25 opened 2 years ago by xyz2277
  0

• The active pods considered by gpu-admission and gpu-manager are inconsistent

  #23 opened 3 years ago by fighterhit
  0

• Error when run build-img.sh

  #21 opened 3 years ago by fajaryanw
  0

• where docs?

  #16 opened 4 years ago by ZeoSophia
  1

• vgpu algorithm based on scheduler framework

  #18 opened 4 years ago by riverzhang
  0

• Scheduler doesn't works with affinity

  #15 opened 4 years ago by josericardomcastro
  1

• Fail on startup

  #12 opened 4 years ago by josericardomcastro
  5

• update pod annotation failed

  #9 opened 4 years ago by fighterhit
  3

• pod xxx had been predicated!

  #8 opened 4 years ago by xs233
  2

• 在有 3 个 gpu 的节点出现调度失败的情况

  #1 opened 5 years ago by scxu
  1

• pod being pending, while node has enough resources

  #5 opened 4 years ago by JasonRD
  0

• some question about the architecture

  #4 opened 4 years ago by JasonRD
  1

• More detailed documentation for running on a kubernetes cluster

  #2 opened 4 years ago by Califax
  1

• when I deployed the gpu-manager, I created one pod as README，the pod's status is UnexpectedAdmissionError!

  #3 opened 4 years ago by 2015-10-10
  1