SriovNetwork can't be create in kube-system namespace

[jeffreyyjp]

Hi guys.
I use below to configue SriovNetwork

apiVersion: sriovnetwork.openshift.io/v1
kind: SriovNetwork
metadata:
  name: sriov-network
  namespace: kube-system
spec:
  ipam: |
    {
      "type": "whereabouts",
      "subnet": "192.168.1.0/24",
      "rangeStart": "192.168.1.200",
      "rangeEnd": "192.168.1.207",
      "gateway": "192.168.1.1",
      "routes": [{
        "dst": "0.0.0.0/0","gw":"192.168.1.1"
      }]
    }
  vlan: 0
  resourceName: mlnxnics

But I can't get a network-attachment-definitions in kube-sytem.

But if I modify the ns in my yaml, I can get

apiVersion: sriovnetwork.openshift.io/v1
kind: SriovNetwork
metadata:
  name: sriov-network
  namespace: sriov-network-operator
spec:
  ipam: |
    {
      "type": "whereabouts",
      "subnet": "192.168.1.0/24",
      "rangeStart": "192.168.1.200",
      "rangeEnd": "192.168.1.207",
      "gateway": "192.168.1.1",
      "routes": [{
        "dst": "0.0.0.0/0","gw":"192.168.1.1"
      }]
    }
  vlan: 0
  resourceName: mlnxnics

[adrianchiris]

you can set spec.networkNamespace to create the network attachment definition in a different namespace.

[SchSeba]

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 namespace he should create the respected net-attach-def

If that is not clear from the readme please let us know and we can improve them.

Let me know if we can close this issue

[jeffreyyjp]

@SchSeba Sure, But from the readme, where we can find the config in these API: https://github.com/k8snetworkplumbingwg/sriov-network-operator?tab=readme-ov-file#api
I think the docs should point it out.

[SchSeba]

Hi @jeffreyyjp you are right we should change the readme