$ oc get nns
OpenShift Virtualization uses
nmstate to report on and configure the state of the node network. This makes it possible to modify network policy configuration, such as by creating a Linux bridge on all nodes, by applying a single configuration manifest to the cluster.
Node networking is monitored and updated by the following objects:
Reports the state of the network on that node.
Describes the requested network configuration on nodes. You update the node network configuration, including adding and removing interfaces, by applying a
NodeNetworkConfigurationPolicy manifest to the cluster.
Reports the network policies enacted upon each node.
OpenShift Virtualization supports the use of the following nmstate interface types:
If your OpenShift Container Platform cluster uses OVN-Kubernetes as the default Container Network Interface (CNI) provider, you cannot attach a Linux bridge or bonding to the default interface of a host because of a change in the host network topology of OVN-Kubernetes. As a workaround, you can use a secondary network interface connected to your host, or switch to the OpenShift SDN default CNI provider.
NodeNetworkState object exists on every node in the cluster. This object is periodically updated and captures the state of the network for that node.
List all the
NodeNetworkState objects in the cluster:
$ oc get nns
NodeNetworkState object to view the network on that node. The output in this example has been redacted for clarity:
$ oc get nns node01 -o yaml
apiVersion: nmstate.io/v1 kind: NodeNetworkState metadata: name: node01 (1) status: currentState: (2) dns-resolver: ... interfaces: ... route-rules: ... routes: ... lastSuccessfulUpdateTime: "2020-01-31T12:14:00Z" (3)
|1||The name of the
|3||Timestamp of the last successful update. This is updated periodically as long as the node is reachable and can be used to evalute the freshness of the report.|