Skip to content

Default networkNamespace for SriovNetwork inapropriate #1093

@djuran

Description

@djuran

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions