Installation prerequisites for Portworx Backup
The minimum supported size for the Portworx Backup cluster is three worker nodes. Each node must meet the following hardware, software, and network requirements:
|CPU||4 CPU cores minimum, 8 cores recommended|
|RAM||4 GB minimum, 8 GB recommended|
|Backend drive||307 GB (In Total)|
NOTE: The above configuration holds good for 2000 backups.
For more information, refer to Portworx Installation Prerequisites.
If you are using an external OIDC provider, you must use certificates signed by a trusted certificate authority.
Make sure helm is installed on the client machine: Helm
If you want to install Portworx Backup on OpenShift using the
restrictedSCC, then you must add the service accounts used by Portworx Backup to the
restrictedSCC. Execute the following
oc adm policy add-scc-to-usercommands, replacing
<YOUR_NAMESPACE>with your namespace:
oc adm policy add-scc-to-user restricted system:serviceaccount:<YOUR_NAMESPACE>:default oc adm policy add-scc-to-user restricted system:serviceaccount:<YOUR_NAMESPACE>:pxcentral-apiserver oc adm policy add-scc-to-user restricted system:serviceaccount:<YOUR_NAMESPACE>:px-keycloak-account oc adm policy add-scc-to-user restricted system:serviceaccount:<YOUR_NAMESPACE>:px-backup-account
NOTE: Portworx Backup 2.3.0 and above use MongoDB 5.x versions internally, which require Intel/AMD chipsets that support Advance Vector Extensions (AVX). If you are deploying Portworx Backup 2.3.0 and above, please ensure that your Intel/AMD chipset versions support AVX.
Prerequisites to install Portworx Backup on Tanzu
Tanzu Kubernetes Grid (TKG) administrators can create deployments, StatefulSets, and DaemonSet (privileged pods) in the kube-system and default namespace, but cannot create in other namespaces. For example, Portworx Backup deployment in the
central namespace fails, because Tanzu Kubernetes clusters include the default
Before you deploy Portworx Backup, for example in the
central namespace, you need to create a rolebinding for privileged and restricted workload deployment using the following commands:
kubectl create ns central
kubectl create rolebinding rolebinding-default-privileged-sa-ns_default --namespace=central --clusterrole=psp:vmware-system-privileged --group=system:serviceaccounts