This week (April 16, 2019), Pure released the 2.4.0 version of the Pure Service
- PSO Operator is now the preferred install method for PSO on OpenShift 3.11 and higher versions.
The PSO Operator packages and deploys the Pure Service Orchestrator (PSO) on OpenShift for dynamic provisioning of persistent volumes on FlashArrays and FlashBlades. The minimum supported version is OpenShift 3.11.
This Operator is created as a Custom Resource Definition from the pure-k8s-plugin Helm chart using the Operator-SDK.
This installation process does not require Helm installation.
- Added flasharray.iSCSILoginTimeout parameter with default value of 20sec.
- Added flasharray.iSCSIAllowedCIDR parameter to list CIDR blocks allowed as iSCSI targets. The default value allows all addresses.
flexPathconfig parameter location in
values.yamlhas been moved from version 2.2.1 from under
orchestratorfield. Upgrading from version earlier than 2.3.0, needs change to
values.yamlto use the new location of
flexPathfor PSO to work.
The Operator is a big change for the install process. We are not leaving or abandoning Helm. I love Helm. Really. This was for our customers that do not allow Helm to run in their environments. Mainly the Tiller pod ran with more permissions than many security teams were comfortable with. Tillerless Helm is coming if you are worried now. The Operator will be the
The flexPath: changing places in the values.yaml is good to know. We wanted to make that setting a
Last but not least, the iSCSIAllowedCIDR limits the iSCSI targets PSO will have the worker node log into during the Persistent Volume mount process. This is important to environments that may serve many different clusters with their own iSCSI networks. The iSCSI interfaces on a FlashArray can be divided with