Enable Pure1 integration for upgrades
This page covers enabling Pure1 integration for the following cases:
- You had a running Portworx cluster prior to Portworx 2.8.0, and you are now upgrading to 2.12.0 or later
- You installed Portworx 2.12.0, but did not enable Pure1 integration and want to do so now
Prerequisites
- Portworx Operator 1.10.0 or later
- A cluster running Portworx 2.12.0 or using an Operator-based installation
- Outbound access to the internet to allow connection to Pure1
If you're using a daemonset-based Portworx installation, you must migrate to an Operator-based install, then:
- If you did not previously enable telemetry for your daemonset-based installation, upgrade to version 2.12 before enabling Pure1 integration.
- If you previously enabled telemetry for your daemonset-based installation, when you migrate that to an Operator-based installation, telemetry is still enabled.
Enable telemetry
Additional configuration for air-gapped clusters
In air-gapped clusters, telemetry is supported via simple or traditional proxy that serves in HTTP mode. If you have a next generation firewall acting as a proxy, or have a problem with the telemetry configuration, contact Portworx Support for assistance.
To enable telemetry, configure a proxy and add it to the PX_HTTP_PROXY or PX_HTTPS_PROXY environment variable in your StorageCluster specification. Telemetry communicates through the specified proxy.
...
spec:
env:
- name: PX_HTTP_PROXY
value: "http://<IP:port>"
- name: PX_HTTPS_PROXY
value: "http://<IP:port>"
...
Portworx supports telemetry in the StorageCluster spec, but it's disabled by default. To enable the metrics collector and telemetry integration with Pure1, add the following section in your StorageCluster spec:
spec:
monitoring:
telemetry:
enabled: true
This adds telemetry components to Portworx and automatically creates the pure-telemetry-certs secret in the <px-namespace> namespace. You can also enable telemetry from Portworx Central via Advanced Settings on the Customize page.
