What is the primary function of the Portworx OCI monitor pod in a Kubernetes environment?

The Portworx OCI monitor (px-oci-mon) is a critical component that runs as a container within the Portworx DaemonSet on each node. Its primary function is to act as a watchdog for the node's health from a storage perspective. It continuously monitors the state of the underlying OCI-compliant container runtime (like containerd or Docker) and the main Portworx service. If it detects that either of these essential services has become unresponsive, it will take corrective action, such as restarting the Portworx container, to restore the node's functionality and ensure the stability of the Portworx storage cluster.

A. To facilitate the installation of Portworx: Installation is handled by the Portworx Operator or by applying Kubernetes spec files, not by the OCI monitor, which operates post-installation.

C. To manage Kubernetes network policies: Network policy enforcement is the responsibility of a Container Network Interface (CNI) plugin (e.g., Calico, Weave), not the Portworx storage layer.

1. Portworx Enterprise Documentation: In the section describing the components

the OCI monitor is explicitly defined. "The Portworx DaemonSet... includes the following containers: ... px-oci-mon: Monitors the OCI container runtime and restarts Portworx if it becomes unresponsive."

Source: Portworx Docs

Reference > Components > Portworx components on Kubernetes.

2. Portworx Enterprise Documentation: The troubleshooting guide for unresponsive nodes implicitly details the role of health monitoring components like the OCI monitor. It explains that if the Portworx daemon on a node becomes unhealthy

the monitor attempts to recover it.

Source: Portworx Docs

Operate and Maintain > Troubleshoot Portworx > Troubleshoot nodes > Node is down.