Upgrading the Hyperscale Compliance Orchestrator (Kubernetes)
If you are upgrading to this version, monitor the Migration Status API to ensure the migration completes successfully. The migration is complete only when the response status is SUCCEEDED. If the API reports an error, generate a support bundle and submit it to Perforce Customer Support for assistance.
Limitation
This release does not support using an external PostgreSQL instance as the Hyperscale database.
Procedure
Perform the following steps to upgrade a Hyperscale Compliance Orchestrator (Kubernetes).
-
Create a new folder named
hyperscale-helm-[version], replacing [version] with the target version:$ mkdir hyperscale-helm-[version] -
Download the Helm chart for the target version into the folder you created in Step 1:
$ cd hyperscale-helm-[version] $ curl -XGET https://dlpx-helm-hyperscale.s3.amazonaws.com/hyperscale-helm-[version].tgz -o hyperscale-helm-[version].tgzThe downloaded file is saved as
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.
Copyhyperscale-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-parquet.yaml
├── values-snowflake.yaml
└── values.yaml -
Configure the
values.yamlandvalues-<connector>.yamlfiles from the new Helm chart by referring to the properties defined in the corresponding files from the previous version. -
After copying the
values.yamlandvalues-<connector>.yamlfiles, there are updates that need to be made to the file under the imageCredentials section:-
If the credentials configured in your
values.yamlhave 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 theHyperscaleCompliancepage on http://download.delphix.com and selecting theHyperscaleHelm Repositorylink. Configure yourvalues.yamlwith the new set of credentials.-
This password update in
values.yamlis 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.
Copy$ docker login --username [USER] --password [PASSWORD] -
Pull Docker images of the Hyperscale Compliance services.
Copy$ 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.
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.
Copy$ helm upgrade -f values-<connector>.yaml hyperscale-helm hyperscale-helm