Closed zhaogaolong closed 3 years ago
Thank you for reporting it. gpushare-scheduler only changes pod metadata. It shouldn't be impacted. https://discuss.kubernetes.io/t/updating-annotations-on-pod/11025
the source of this issue is an old client-go dependency as you mention. I had the same issue.
This fork solves this relatively ok: https://github.com/k8s-gpushare/gpushare-scheduler-extender
yes, I was fixed. please close this issues
@zhaogaolong how you fixed it?
@zhaogaolong How did you solve this problem?Can you tell us a little bit about it? Thank you
That's how we use it,Configure the gpushare parameters in the YAML file of Kubernetes,But it was wrong.Please tell us how to fix this GPU usage method. Thank you
This error: Binding rejected: failed bind with extender at URL http://192.168.1.1:32766/gpushare-scheduler/bind, code 500
the YAML file of Kubernetes: resources: requests: cpu: 1000m memory: 1000Mi limits: cpu: 2000m memory: 4096Mi aliyun.com/gpu-count: 1 aliyun.com/gpu-mem: 2
envs & version
kubernetes: 1.17 scheduler extender: k8s-gpushare-schd-extender:1.11-d170d8a
errors log
I suspect it is a version of the dependency kube client go version too old. in GOpkg.toml
but this version can't support kubernetes 1.17