Skip to content

OpenShift

To upgrade NEOGAGE requires obtaining the latest helm chart, which can be obtained from your Account Manager. Then, ensure that it is completed with the values used during the initial deployment:

clusterName: os.upware.pl
replicaCount: 1
strategy: Recreate
image:
repository: registry.upware.pl/neogage/neogage
pullPolicy: IfNotPresent
tag: "3.7.0"
imagePullSecrets:
name: image-registry-secret
pvc:
data:
name: neogage-data
accessMode: ReadWriteOnce
storage: 10Gi
volumeMode: Filesystem
volumes:
- name: neogage-data
persistentVolumeClaim:
claimName: neogage-data
- name: neogage-secrets
secret:
secretName: neogage-secrets
volumeMounts:
- name: neogage-data
mountPath: "/var/www/neogage/data"
- name: neogage-secrets
mountPath: "/etc/neogage"
readOnly: true
# Set to your requirements from when MSSQL Server was deployed
secrets:
sql_db_app: neogage_master
sql_db_data: neogage_data
sql_instance: ""
sql_password: MySecretPassword123!
sql_port: 1433
sql_server: mssql-server
sql_user: sa

In most cases, this will only require updating:

  • OpenShift clusterName value
  • SQL database information

Once this matches the information used during initial installation, upgrade NEOGAGE by running the following command:

Terminal window
helm upgrade neogage . -n neogage

Once NEOGAGE is running again, check and verify everything is working as expected. Helm also gives the ability to rollback to previous versions if the application isn't working as expected.