The spec.networkNamespace of the SriovNetwork CR describes which NS the resulting net-attach-defs should end up in, i.e. where the VFs will be consumed by the application. As such, this will never be "openshift-sriov-network-operator" but rather the NS in which the application runs.
I suggest removing this parameter from the template which, if I'm not mistaken, will create the net-attach-defs in the default NS.,
|
networkNamespace: openshift-sriov-network-operator |
The spec.networkNamespace of the SriovNetwork CR describes which NS the resulting net-attach-defs should end up in, i.e. where the VFs will be consumed by the application. As such, this will never be "openshift-sriov-network-operator" but rather the NS in which the application runs.
I suggest removing this parameter from the template which, if I'm not mistaken, will create the net-attach-defs in the default NS.,
cnf-features-deploy/ztp/source-crs/SriovNetwork.yaml
Line 10 in 05c581a