bb81101570
If device plugin returns device without topology, keep it internaly as NUMA node -1, it helps at podresources level to not export NUMA topology, otherwise topology is exported with NUMA node id 0, which is not accurate. It's imposible to unveile this bug just by tracing json.Marshal(resp) in podresource client, because NUMANodes field ID has json property omitempty, in this case when ID=0 shown as emtpy NUMANode. To reproduce it, better to iterate on devices and just trace dev.Topology.Nodes[0].ID. Signed-off-by: Alexey Perevalov <alexey.perevalov@huawei.com>
29 lines
720 B
YAML
29 lines
720 B
YAML
apiVersion: apps/v1
|
|
kind: DaemonSet
|
|
metadata:
|
|
labels:
|
|
name: kubevirt-kvm-device-plugin
|
|
name: kubevirt-kvm-device-plugin
|
|
spec:
|
|
selector:
|
|
matchLabels:
|
|
name: kubevirt-kvm-device-plugin
|
|
template:
|
|
metadata:
|
|
labels:
|
|
name: kubevirt-kvm-device-plugin
|
|
spec:
|
|
containers:
|
|
- name: kubevirt-kvm-device-plugin
|
|
image: quay.io/kubevirt/device-plugin-kvm
|
|
args: ["-v", "3", "-logtostderr"]
|
|
securityContext:
|
|
privileged: true
|
|
volumeMounts:
|
|
- name: device-plugin
|
|
mountPath: /var/lib/kubelet/device-plugins
|
|
volumes:
|
|
- name: device-plugin
|
|
hostPath:
|
|
path: /var/lib/kubelet/device-plugins
|