nokia/CPU-Pooler

Issues

• webhook:x509: certificate signed by unknown authority

  #81 opened a year ago by x-coder-L
  0

• CPU-Pooler fail to start because of PodSecurityPolicy restrictions.

  #40 opened a year ago by adamdembek
  1

• System processes/daemons

  #76 opened a year ago by maxpain
  21

• Support for cgroupv2

  #77 opened a year ago by gmarkey
  2

• does not match to expected cpuset

  #68 opened 3 years ago by antzjm
  6

• CPU-Pooler breaks with K8s 1.21 and onward

  #65 opened 3 years ago by Levovar
  1

• Cpu affinity conflicts with cgroups configuration when create pod with exclusive-pool

  #64 opened 3 years ago by yjy5921591ok
  5

• Compilation error caused by code syntax error

  #63 opened 3 years ago by yjy5921591ok
  2

• Allocatable cpu resource will be lost when kubelet restart

  #58 opened 3 years ago by antzjm
  11

• x509: certificate relies on legacy Common Name field, use SANs or temporarily enable Common Name matching with GODEBUG=x509ignoreCN=0

  #57 opened 3 years ago by waynezhang1984
  5

• Hyperthreading support

  #31 opened 3 years ago by Levovar
  2

• Set limits and requests for exclusive pool containers

  #25 opened 3 years ago by Levovar
  6

• Align memory allocations to exclusive CPU socket

  #54 opened 4 years ago by Levovar
  1

• Potential import collision: import path should be "gopkg.in/yaml.v2", not "github.com/go-yaml/yaml".

  #50 opened 4 years ago by KateGo520
  3

• Help needed regarding cpu-pooler-configmap.yaml

  #51 opened 4 years ago by shubham-gaur
  3

• Build step of 'dep ensure --vendor-only' failed for not find project of Gopkg.toml

  #48 opened 4 years ago by abiao610
  4

• Try to build docker image of webhook but the step of 'ADD Gopkg.* ./' failed

  #45 opened 4 years ago by abiao610
  2

• Container restarted due to Cgroup cpuset does not match to expected cpuset

  #44 opened 4 years ago by YanXiaoping2
  2

• Support Topology Manager

  #24 opened 4 years ago by Levovar
  1

• Asking exclusive and shared resources at the same time can sometimes result in Pod startup failure

  #36 opened 5 years ago by Levovar
  8

• Is the nokia CPU Pooler can coordinate well with CPU Manager in kubernetes?

  #35 opened 5 years ago by andyzheung
  5

• About why use the pinner binary to pin cpu for a process?

  #33 opened 5 years ago by andyzheung
  3

• Requesting multiple thousand of shared cpu cycles causes parsing error

  #27 opened 5 years ago by TothFerenc
  1

• cpu device plugin daemon set cannot get resources "nodes"

  #19 opened 5 years ago by maxcaresywwforever
  2

• cpusetter fail to set container cpuset for multi-containers pod

  #29 opened 5 years ago by maxcaresywwforever
  2

• Support containers asking for resources from multiple Pooler managed pools

  #17 opened 5 years ago by Levovar
  3

• CPUSetter does not adjust its own cpuset

  #20 opened 5 years ago by Levovar
  2

• Automatically adjust the cpuset of the pause container to the default pool

  #21 opened 5 years ago by Levovar
  1

• Device Plugin misinterprets cpusets supplied in the standard Linux "range" notation

  #12 opened 5 years ago by Levovar
  1

• Webhook wrongly patches "request" into a shared pool user's manifest

  #14 opened 5 years ago by Levovar
  0

• Issues related to handling shared pool

  #10 opened 5 years ago by Levovar
  0

• Support multiple shared pools

  #11 opened 5 years ago by Levovar
  0

• Add validation of CPU-Pooler related fields in pod manifest

  #1 opened 6 years ago by TimoLindqvist
  0