Upgrading the Hyperscale Compliance Orchestrator (OpenShift)

Perform the following steps to upgrade a Hyperscale Compliance Orchestrator (OpenShift).

Create a new folder called hyperscale-helm-[version], where [version] is the latest version to which the platform is being upgraded.
$ mkdir hyperscale-helm-[version]
Download the new version of the chart using the following command in tandem with the newly created folder. Note: This command will download a file named hyperscale-helm-[version].tgz in the folder hyperscale-helm-[version].
CODE
```
$ cd hyperscale-helm-[version]
$ curl -XGET https://dlpx-helm-hyperscale.s3.amazonaws.com/hyperscale-helm-[version].tgz -o hyperscale-helm-[version].tgz
```
The downloaded file is then extracted using the following command.
$ tar -xvf hyperscale-helm-[version].tgz

This will extract into the following directory structure.

CODE

hyperscale-helm
    ├── Chart.yaml
    ├── README.md
    ├── templates
        │-<all templates files>
    ├── tools
        │-<all tool files>
    ├── values-file-connector.yaml
    ├── values-mongo.yaml
    ├── values-mssql.yaml
    ├── values-oracle.yaml
    └── values.yaml

Copy the values.yaml and values-<connector>.yaml files from the previous version parallel to the hyperscale-helm-[version] folder.
1. If upgrading from a Delimited/Parquet Files connector, then the image name has been changed to file-connector. As Parquet/Delimited File connectors have been merged into the File Connector, the new connector name will be file-connector.
After copying the values.yaml and values-<connector>.yaml files, there are updates that need to be made to the file under the imageCredentials section:
- Bumping up the version, specified against the tag property, to the desired higher version.
- If the credentials configured in your values.yaml have expired, which will be the case if the credentials were unused for 30 days or were inactive (but previously used) for 90 days, please retrieve a new set of credentials by visiting the Hyperscale Compliance page on http://download.delphix.com and selecting the Hyperscale Helm Repository link. Configure your values.yaml with the new set of credentials.
  - This password update in values.yaml is only required if the user is using a Delphix-provided Docker Registry (hyperscale.download.delphix.com/delphix-hyperscale) directly in the deployment (i.e. values.yaml).
  - If you are using your internal Docker Registry, you should first pull the next version of the Docker images from the Delphix-provided registry with the credentials associated with your Delphix account.
  - The following are the ‘docker’ commands that can be used to pull Docker images into your internal Docker Registry:
    - Docker login command (username and password are your permanent credentials retrieved from Delphix Download site).
      CODE
      
      $ docker login --username [USER] --password [PASSWORD]
    - Pull Docker images of the Hyperscale Compliance services.
      CODE
      
      $ docker pull <image-url>
The image URLs for the Hyperscale Compliance services can be referenced from this page of the documentation.
Provide the values for NFS/AWS S3 related parameters to setup the mount-filesystem.

Upon application startup, all existing mount-filsystems will be deleted. Please ensure to take backup of the mount setup details, if needed.

If upgrading from a version <= 23.0.0 and the staging area volume has been configured via NFS storage, ensure that all of the following parameters have been set in the values.yaml file of the latest version's helm chart bundle:

nfsStorageHost - Set this to the same value as set in the previous version's helm chart values.
nfsStorageExportPath - Set this to the same value as set in the previous version's helm chart values.
nfsStorageMountType - Set this to one of applicable values(NFS4, NFS3, CIFS).

Run the helm upgrade command.
$ helm upgrade -f values-<connector>.yaml hyperscale-helm hyperscale-helm