Sebastian Scheinkman
Sebastian Scheinkman
Hi @zeeke @e0ne @adrianchiris please help move this one forward it's a critical feature I would like to get in as soon as possible. Thanks!
Hi @adrianchiris when you have time please take another look :)
ping @zeeke @adrianchiris :)
Hi @e0ne @adrianchiris I updated the design based on the actual implementation we just merged. please take a look when you have time :)
Merging this one
that is a kubernetes feature. you can configure device manager and check the topology type https://kubernetes.io/docs/tasks/administer-cluster/topology-manager/#policy-single-numa-node
Hi @cyclinder, do you think we can close this issue? I don't think there is something the sriov-operator can do about this. I think for now the only solution is...
do we also need to bump the version when we remove it?
Hi @jeffreyyjp, The sriovNetwork MUST be created in the namespace where the operator is running. and as commented by @adrianchiris you can use `spec.networkNamespace` to tell the operator on which...
Hi @jeffreyyjp you are right we should change the readme