PowerProtect Data Manager 19.17 Kubernetes User Guide
powerprotect-controller pod not created due to security policy configuration
If your security policy configuration prevents the powerprotect-controller pod creation, set the Pod Security Admission level for the powerprotect and velero-ppdm namespaces to privileged by running the following:
kubectl label --overwrite ns powerprotect pod-security.kubernetes.io/enforce=privileged
kubectl label --overwrite ns velero-ppdm pod-security.kubernetes.io/enforce=privileged
NOTE: If the
velero-ppdm namespace does not yet exist, wait a few moments after setting the
powerprotect namespace level for the namespace to appear. The
powerprotect-controller pod creates the
velero-ppdm namespace after startup.
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please select whether the article was helpful or not.
Comments cannot contain these special characters: <>()\