This documentation is for a release that is no longer maintained
See documentation for the latest supported version 3 or the latest supported version 4.第 11 章 Node networking
11.1. Observing node network state 复制链接链接已复制到粘贴板!
Node network state is the network configuration for all nodes in the cluster.
11.1.1. About nmstate 复制链接链接已复制到粘贴板!
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:
NodeNetworkState
- Reports the state of the network on that node.
NodeNetworkConfigurationPolicy
-
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. NodeNetworkConfigurationEnactment
- Reports the network policies enacted upon each node.
OpenShift Virtualization supports the use of the following nmstate interface types:
- Linux Bridge
- VLAN
- Bond
- Ethernet
11.1.2. Viewing the network state of a node 复制链接链接已复制到粘贴板!
A NodeNetworkState
object exists on every node in the cluster. This object is periodically updated and captures the state of the network for that node.
Procedure
List all the
NodeNetworkState
objects in the cluster:oc get nns
$ oc get nns
Copy to Clipboard Copied! Toggle word wrap Toggle overflow Inspect a
NodeNetworkState
to view the network on that node. The output in this example has been redacted for clarity:oc get nns node01 -o yaml
$ oc get nns node01 -o yaml
Copy to Clipboard Copied! Toggle word wrap Toggle overflow Example output
Copy to Clipboard Copied! Toggle word wrap Toggle overflow - 1
- The name of the
NodeNetworkState
is taken from the node. - 2
- The
currentState
contains the complete network configuration for the node, including DNS, interfaces, and routes. - 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.