-
Notifications
You must be signed in to change notification settings - Fork 176
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
Hanging resource name after edit configmap #245
Comments
This seems to be related to the kubelet side of things, as it does not remove resources from node that are no longer reported by device plugin but rather updates their capacity/allocatable to 0 |
Thx for ur reply. |
its just from skimming through the kubelet code so you would need to confirm that from kubelet side. Also in general a device plugin reports to kubelet resources that it has not the ones that it doesn't :) |
It'll be interesting to see what the feedback is from the kubelet side - I have had this issue with running fuzz tests on device plugins which leaves !hundreds of 0 resources listed as part of the node info object. |
What happened?
Deploy "sriov-network-device-plugin" with default configmap as
After all Pods are running, delete old configmap and create a new configmap with as following:
and restart all sriov network device plugin Pods in order to take new configmap into use.
but from the node "status.allocatable" we still see the entry with resouceName in old configmap.
What did you expect to happen?
The node "status.allocatable" entries should be updated with new configmap only.
Or we would like to know whether this is expected behavior.
What are the minimal steps needed to reproduce the bug?
Anything else we need to know?
Component Versions
Please fill in the below table with the version numbers of components used.
Config Files
Config file locations may be config dependent.
Device pool config file location (Try '/etc/pcidp/config.json')
Multus config (Try '/etc/cni/multus/net.d')
CNI config (Try '/etc/cni/net.d/')
Kubernetes deployment type ( Bare Metal, Kubeadm etc.)
Bare Metal
Kubeconfig file
SR-IOV Network Custom Resource Definition
Logs
SR-IOV Network Device Plugin Logs (use
kubectl logs $PODNAME
)Multus logs (If enabled. Try '/var/log/multus.log' )
Kubelet logs (journalctl -u kubelet)
The text was updated successfully, but these errors were encountered: