An infrastructure admin wants to restrict installing Portworx on two nodes. What label does the node need to have?

To prevent Portworx from being installed on a specific node, an administrator must apply the px/enabled=false label to that Kubernetes node. The Portworx Operator and DaemonSet are configured with a node affinity rule that actively avoids scheduling Portworx pods on any node carrying this specific label. This is the designated method for explicitly excluding nodes from a Portworx installation, ensuring that the Portworx components are never deployed to them.

A. px/service=stop: This label is used to stop the Portworx service on a node where it is already installed and running, typically for maintenance, not to prevent the initial installation.

C. px/storage-node=false: This label designates a node as "storageless." Portworx is still installed on such nodes, but they do not contribute storage to the cluster; they only provide volume access.

1. Portworx Enterprise Documentation

"Exclude nodes from Portworx installation": "To prevent Portworx from installing on a specific node

apply the px/enabled=false label to that node. The Portworx DaemonSet uses a node selector to avoid nodes with this label." (Found under Install and Configure -> Install Portworx -> Install on Kubernetes -> On-premises -> Operator -> Customize the Operator install).

2. Portworx Enterprise Documentation

"Storageless nodes": "You can configure Portworx to run on storageless nodes by applying the px/storage-node=false label to them. Portworx still runs on these nodes

but they do not contribute any storage to the storage cluster." (Found under Storage Management -> Storageless nodes).

3. Portworx Enterprise Documentation

"Enter maintenance mode": "To place a node in maintenance mode

enter the following kubectl label command... kubectl label node px/service=stop --overwrite" (Found under Operate and Maintain -> Maintenance -> Decommission a node -> Enter maintenance mode).