k8s.v1.cni.cncf.io/networks annotation and what Multus attached in k8s.v1.cni.cncf.io/network-status. OpenShift uses the same annotations for its secondary networks.
What Radar Shows
Detail View: A Pod’s Secondary Networks section lists each attachment with its interface, every IP address (so a dual-stack attachment shows both), MAC address and a default-network marker. Each row is labelled Reported when thenetwork-status annotation lists it, Requested only when it does not, and a reported attachment that nothing requested says so. A definition name links to its NetworkAttachmentDefinition when Radar can read it; otherwise the row says the definition was not found, that you lack permission to read it, or that it could not be checked.
The networks annotation may be a comma-separated list (name, namespace/name, name@interface) or a JSON list. A definition attached more than once appears once per attachment. A name without a namespace is read as the Pod’s namespace. An annotation Radar cannot read is shown with the reason and its raw value, never as “no networks”. The section does not appear for a Pod that only has its default network, which is every Pod on some clusters.
Requested is not attached, and a reported interface does not show that the Pod can reach anything on that network.
Helm: rbac.crdGroups.multus (default on) grants read on network-attachment-definitions in k8s.cni.cncf.io, and nothing else in that group.
Topology, Issues, MCP summaries and MultiNetworkPolicy are not covered.