The Kubernetes Inventory Agent recognizes accurate worker node inventory for Red Hat OpenShift Container Platform clusters
Note:This enhancement is available with IT Asset Management.
In this release, the Flexera Kubernetes Inventory Agent has been further enhanced to recognize accurate worker node inventory in a Kubernetes cluster for Red Hat OpenShift. Prior to this enhancement, the Flexera Kubernetes Inventory Agent collected inventory data pertaining to the Kubernetes container, instead of collecting inventory data for the actual worker node that the Kubernetes container was deployed to.
On collecting accurate worker node inventory data, for any installed application(s) imported into IT Asset Management that are subscribed to and paid for, you can now license these applications accordingly by creating a license for the application(s) to consume against.
This enhancement is supported by the Standard Flexera Kubernetes Inventory Agent (often referred to as the "full" Flexera Kubernetes Inventory Agent), and the Lightweight Kubernetes Inventory Agent. Installer evidence will be updated to reflect new inventory, and inventory that is no longer present will be removed each and every time the Flexera Kubernetes Inventory Agent collects inventory from a Kubernetes cluster(s) in your environment.
Notable changes
| • | The hostname of a Kubernetes worker node is now visible in the IT Asset Management UI in all contexts where an operator is viewing details about a worker node (All Inventory, Inventory Device Properties, Custom Reports, and so on). Prior to this change, the Kuberenetes node unique identifier for the worker node was displayed in the hostname column on the All Containers page. |
| • | The operating system of a Kubernetes worker node is now visible on any page in the IT Asset Management UI which shows the operating system of an inventory device (All Inventory, Inventory Device Properties, Custom Reports, and so on). Prior to this change, the reported operating system was the operating system of the Kubernetes container that was used to collect inventory rather than the actual operating system installed on the worker node. To support this change, a new property called OSImage was added to the MGS_KubernetesNode class which is uploaded as part of the primary Kubernetes resource inventory. For more information on the MGS_KubernetesNode class, see Kubernetes Inventory Uploads in the Gathering FlexNet Inventory user guide. |
| • | Red Hat OpenShift subscription components in your Kubernetes cluster environments can now be recognized using the full and Lightweight Kubernetes Inventory Agent. After inventory has been collected, subscription component data is mapped over to IT Asset Management and can be viewed from the All Containers page (Inventory > All Containers). |
How to enable software inventory to be collected
In order to collect software inventory from a worker node (operating system and other applications that are installed on the worker node), there are two Flexera Kubernetes Inventory Agent attributes that need to be enabled: The mountHostFS attribute and the collectHostRpmInfo attribute. For details on how to enable these attributes, see Attributes for Agent Features in the Help.
Red Hat OpenShift worker nodes based on RHEL CoreOS are immutable, and software inventory for these nodes will be collected by allowing the Flexera krm daemonset (which runs on all nodes) to mount file paths on the node host itself as read-only mounts. The operating system data and installed RPM packages are then reported in the k8s-node NDI.
For information on how to download and install the Flexera Kubernetes Inventory Agent, see Download Flexera Kubernetes Inventory Agent in the Help.