We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
v0.8.0
Other
no
after uninstalling spiderpool , still some sriov pod is running
kube-system sriov-device-plugin-dwlj9 1/1 Running 0 24h kube-system sriov-device-plugin-whdgf 1/1 Running 0 24h kube-system sriov-network-config-daemon-mwprv 3/3 Running 15 (24h ago) 30h kube-system sriov-network-config-daemon-tcv7w 3/3 Running 15 (24h ago) 30h
unisntall them
simple
No response
The text was updated successfully, but these errors were encountered:
I'll finish it in this release
Sorry, something went wrong.
k8snetworkplumbingwg/sriov-network-operator#430
k8snetworkplumbingwg/sriov-network-operator#564
sriov CRD remnant fixed in #3339.
The new version of sriov-operator-network has fixed this issue.
cyclinder
taoyounger
No branches or pull requests
Spiderpool Version
v0.8.0
Bug Type
Other
Main CNI
no
What happened?
after uninstalling spiderpool , still some sriov pod is running
kube-system sriov-device-plugin-dwlj9 1/1 Running 0 24h
kube-system sriov-device-plugin-whdgf 1/1 Running 0 24h
kube-system sriov-network-config-daemon-mwprv 3/3 Running 15 (24h ago) 30h
kube-system sriov-network-config-daemon-tcv7w 3/3 Running 15 (24h ago) 30h
What did you expect to happen?
unisntall them
How to reproduce it (as minimally and precisely as possible)
simple
Additional Context
No response
The text was updated successfully, but these errors were encountered: