Sebastian Scheinkman comments

Results 287 comments of


                                            Sebastian Scheinkman

panic: runtime error: invalid memory address or nil pointer dereference

closing this one

Parallelize the SRIOV configuration on multiple nodes

should be fixed via https://github.com/k8snetworkplumbingwg/sriov-network-operator/pull/555

Parallelize the SRIOV configuration on multiple nodes

the PR is merged closing this one

Release SRIOV Network Operator V1.3.0

I added the parallel draining into the list

Release SRIOV Network Operator V1.3.0

closing this one as we made a release

If the pod expulsion or removal fails during the nodedrain operation, the entire node will be schdulingDisabled

Hi @lizhewei91 the reason is to be sure no new workloads will be allocated on the node in the time we are doing the configuration. you can have many race...

If the pod expulsion or removal fails during the nodedrain operation, the entire node will be schdulingDisabled

Hi please take a look on the new draining capabilities we are working on https://github.com/k8snetworkplumbingwg/sriov-network-operator/pull/555 be aware that if the policy doesn't work the node will continue to retry but...

If the pod expulsion or removal fails during the nodedrain operation, the entire node will be schdulingDisabled

no update for a long time closing this issue

How can I query which VF is allocated to which pod?

you should also be able to see in the pod `network-status` annotation the PCI address

How can I query which VF is allocated to which pod?

@Panlichen did the comments help? can we close this issue?