Pure Service Orchestrator (PSO) Helm Charts
Pure Service Orchestrator 5.x, which is instaled using this Helm chart (pure-csi), is in feature freeze. All new features will be going into our new 6.x release (pso-csi). Bug reports for 5.x will still be addressed, and PSO 5.x (pure-csi) is currently still the required plugin for Google Anthos and OpenShift 3.11.
What is PSO?
Pure Service Orchestrator (PSO) delivers storage-as-a-service for containers, giving developers the agility of public cloud with the reliability and security of on-premises infrastructure.
PSO automatically makes the best provisioning decision for each storage request – in real-time – by assessing multiple factors such as performance load, the capacity and health of your arrays, and policy tags.
Uniting all your Pure FlashArray™ and FlashBlade™ arrays on a single shared infrastructure, and supporting file and block as needed, PSO makes adding new arrays effortless, so you can scale as your environment grows.
To ensure your services stay robust, PSO self-heals – so you’re protected against data corruption caused by issues such as node failure, array performance limits, and low disk space.
Operating Systems Supported*:
- CentOS 7
- CoreOS (Ladybug 1298.6.0 and above)
- RHEL 7
- Ubuntu 16.04
- Ubuntu 18.04
- Refer to the README for the type of PSO installation required
Other software dependencies:
- Latest linux multipath software package for your operating system (Required)
- Latest Filesystem utilities/drivers (XFS by default, Required)
- Latest iSCSI initiator software for your operating system (Optional, required for iSCSI connectivity)
- Latest NFS software package for your operating system (Optional, required for NFS connectivity)
- Latest FC initiator software for your operating system (Optional, required for FC connectivity, FC Supported on Bare-metal K8s installations only)
FlashArray and FlashBlade:
- The FlashArray and/or FlashBlade should be connected to the compute nodes using Pure's best practices
FlashArray User Privilages
- It is recommend to use a specific FlashArray user, and associated API token, for PSO access control to enable easier array auditing.
- The PSO user can be local or based on a Directory Service controlled account (assuming DS is configured on the array).
- The PSO user requires a mininum role level of
FlashBlade User Privileges
- If the FlashBlade is configured to use Directory Services for array management, then a DS controlled account and its associated API token can be used for PSO.
- The PSO user requires a mininum array management role level of
- Currently ther is no option to create additonal local users on a FlashBlade.
* Please see release notes for details
PSO can be used with any of the following hardware appliances and associated minimum version of appliance code:
- Pure Storage FlashArray (minimum Purity code version 4.8)
- Pure Storage FlashBlade (minimum Purity version 2.2.0)
PSO can be deployed via an Operator or from the Helm chart.
PSO has Operator-based install available for both its FlexVolume (deprecated) plugin and CSI plugin. This install method does not need Helm installation.
Pure Flex Operator is the preferred installation method for FlexVolume on OpenShift version 3.11. The CSI Operator should be used for OpenShift 4.1 and 4.2.
Note Use the CSI Helm3 install method for OpenShift 4.3 and higher with the adoption of Helm3 in OpenShift.
pure-k8s-plugin deploys PSO FlexVolume plugin on your Kubernetes cluster - the Flex Driver is now deprecated
pure-csi deploys PSO CSI plugin on your Kubernetes cluster.
Install Helm by following the official documents:
In OpenShift 3.11 the Red Hat preferred installation method is using an Operator. Follow the instructions in the PSO operator directory.
PSO on the Internet
We welcome contributions. The PSO Helm Charts project is under Apache 2.0 license. We accept contributions via GitHub pull requests.
Report a Bug
For filing bugs, suggesting improvements, or requesting new features, please open an issue.