search

k8snetworkplumbingwg / sriov-network-device-plugin

SRIOV network device plugin for Kubernetes
Apache License 2.0
408 stars 177 forks source link

update sriov-crd fail #563

Closed a576266 closed 5 months ago

a576266 commented 5 months ago

What happened?

Let me tell you an incident. vim sriov-network-device-plugin/deployments/sriov-crd.yaml Modify the k8s.v1.cni.cncf.io/resourceName: in this to lucas.com/lucas_vf_k8s But lucas.com is not effective here, it is still intel.com

What did you expect to happen?

update success

What are the minimal steps needed to reproduce the bug?

Anything else we need to know?

I also want to ask, I created a vf on a single node and assigned it to two pods, but the network ports assigned by calico cannot communicate. The network ports of vf can communicate with each other. Why? I want both network ports to communicate. Do you have any suggestions? Thank you

Component Versions

Please fill in the below table with the version numbers of components used.

Component Version
SR-IOV Network Device Plugin
SR-IOV CNI Plugin
Multus
Kubernetes
OS

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.)
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)