PowerProtect Data Manager - nodeSelector is not working for Velero pod for OpenShift
Summary: PowerProtect Data Manager - nodeSelector is not working for Velero pod for OpenShift.
This article applies to
This article does not apply to
This article is not tied to any specific product.
Not all product versions are identified in this article.
Symptoms
For OCP cluster, when you set nodeSelector in the Asset source pod configuration for velero as following example:
--- spec: template: metadata: annotations: k8s.v1.cni.cncf.io/networks: network1 spec: nodeSelector: node-role.kubernetes.io/xxxxx
After velero pod is created, the nodeSelector is still showing as none and it cannot be running on the requested node:
Node-Selectors: <none>Cause
Since this is an OCP cluster and the OADP operator controls the Velero, PowerProtect Data Manager does not have control to edit the velero pod.
Resolution
Manually edit the DataProtectionApplication as showing below and add nodeSelector manually. Once make below change, the velero pod is re-created on the specified node.
oc edit DataProtectionApplication oadp-velero -n velero-ppdm

Request to edit node names as per their configuration.
Affected Products
PowerProtect Data ManagerProducts
PowerProtect Data Manager Essentials, PowerProtect SoftwareArticle Properties
Article Number: 000273499
Article Type: Solution
Last Modified: 22 Jan 2026
Version: 4
Find answers to your questions from other Dell users
Support Services
Check if your device is covered by Support Services.