In a modern Portworx deployment on Kubernetes managed by an Operator, the standard and recommended method for verification is through Kubernetes-native tooling. The kubectl get storagenodes command queries the StorageNode Custom Resource Definition (CRD), which is the authoritative representation of the Portworx nodes within the Kubernetes API. The output directly displays the status, and most importantly, the VERSION of the Portworx software on each node. This aligns with the declarative, Operator-driven management paradigm, which is the current best practice for running complex stateful services on Kubernetes.

A. pxctl get storagenodes: While this command provides similar information by querying the Portworx daemon directly, the Kubernetes-native approach (kubectl) is the recommended practice for verification in modern, Operator-managed environments.

C. kubectl get nodes -o wide: This command displays information about the Kubernetes cluster nodes (like OS and kernel version), not the version of the Portworx application running on them.

1. Portworx Enterprise Documentation

"Upgrade Portworx on Kubernetes using the Operator": In the section "Verify the Portworx upgrade

" the documentation explicitly instructs the administrator to use kubectl: "Verify that all Portworx pods are running the upgraded version... You can verify this by running the kubectl get storagenodes -n kube-system command and looking at the VERSION column."

2. Portworx Enterprise Documentation

"Monitor Portworx on Kubernetes": In the section "Monitor Portworx components

" the documentation states: "The Portworx Operator creates StorageNode and StorageCluster objects... You can view the status of your storage nodes by running the kubectl get storagenodes command." This reinforces that querying the StorageNode CRD is the standard monitoring and verification procedure.

3. Kubernetes Documentation

"Custom Resources": This documentation explains the concept of Custom Resource Definitions (CRDs) and how kubectl is the standard tool for interacting with these resources. The StorageNode object is a CRD installed by Portworx

making kubectl get storagenodes the correct

Kubernetes-native interaction pattern.