Description of problem (please be detailed as possible and provide log
snippests):

The ODF must-gather does not collect NetworkAttachmentDefinitions that affect Multus. The must-gather should be updated to collect NetworkAttachmentDefinition resources from the "default" and "openshift-storage" namespaces.


Version of all relevant components (if applicable):

I would hope this can be part of an upcoming 4.13.z release.


Does this issue impact your ability to continue to work with the product
(please explain in detail what is the user impact)?

No.


Is there any workaround available to the best of your knowledge?

OCP must-gather collects NetworkAttachmentDefinitions


Rate from 1 - 5 the complexity of the scenario you performed that caused this
bug (1 - very simple, 5 - very complex)?
1


Can this issue reproducible? Yes.


Can this issue reproduce from the UI? N/A


If this is a regression, please provide more details to justify this: N/A


Steps to Reproduce:
It is not necessary to install ODF with multus enabled to repro!

First, create these two NetworkAttachmentDefinitions:

  apiVersion: k8s.cni.cncf.io/v1
  kind: NetworkAttachmentDefinition
  metadata:
    name: cluster-net
    namespace: openshift-storage
  spec:
    config: '{ "cniVersion": "0.3.1", "type": "macvlan", "master": "br-ex", "mode":
      "bridge", "ipam": { "type": "whereabouts", "range": "192.168.30.0/24" } }'

  apiVersion: k8s.cni.cncf.io/v1
  kind: NetworkAttachmentDefinition
  metadata:
    name: cluster-net
  spec:
    config: '{ "cniVersion": "0.3.1", "type": "macvlan", "master": "br-ex", "mode":
      "bridge", "ipam": { "type": "whereabouts", "range": "192.168.30.0/24" } }'


Next, collect an ODF must-gather

Both NADs should be collected but are not. The first NAD is in the openshift-storage NS, and the second is in the default NS. NADs from other NSes do not need to be collected for ODF.