PDS supports Vanilla Kubernetes, AWS EKS, and Azure Kubernetes Service (AKS).
- PDS account Admin privileges
- A supported Kubernetes cluster with Portworx Enterprise installed on it.
- Helm chart version 3.2.0 or newer
Prepare your cluster for installation
In the Settings → Deployment Targets page → select the Add Deployment Target button.
From the How to Add Deployment Targets window, copy the
helm installcommand and paste it into a secure text editor.note
Do not modify the
Wait for the PDS agent to register the new deployment target in the control plane. Once successful, the status will show as a green check mark.
Prepare namespaces for deployment
After adding a target cluster to PDS, you must make any namespaces you intend to use with PDS available to it. Perform this task for each namespace you want to create and add:
NAMESPACEenvironment variable with the namespace you want to create or add:
Create the namespace, if it does not exist:
kubectl create namespace $NAMESPACE
Label the namespace:
kubectl label namespaces $NAMESPACE pds.portworx.com/available=true --overwrite=true
Once successful, the No namespaces available error message will disappear.
Disconnected deployment target
If a deployment target registration is unsuccessful, then the status will show as Disconnected. A deployment target becomes disconnected due to one or a combination of the following reasons:
- If Portworx is not installed, then the PDS agent fails to start.
- PDS agent fails to connect to the control plane.
- PDS agent fails to register the target cluster.
- Teleport agent fails to start.
- Teleport agent fails to connect to the control plane.
- Teleport agent fails to register the target cluster.
- Teleport agent fails to establish a secure reverse tunnel.
View the deployment target health
Run the following commands to learn more about the healthiness of a target cluster deployment:
Learn more about the PDS agent deployment
Describe PDS Agent deployment:
kubectl describe deployment/pds-agent -n pds-system
Check logs of PDS agent:
kubectl logs deployment/pds-agent -n pds-system
Learn more about the Teleport deployment
Describe Teleport deployment:
kubectl describe deployment/pds-teleport -n pds-system
Check logs of Teleport:
kubectl logs deployment/pds-teleport -n pds-system
In the Settings -> Deployment Targets page, you can select any Disconnected deployment target to view the reasons for a cluster getting disconnected: