Prerequisites for Upgrading on Azure
Verify the following before performing the upgrade :
-
The packages for upgrade have been downloaded following this procedure:
-
To identify the files to download to your secure network location, see Downloading the files in the Release Notes for ArcSight Platform 23.3.
-
From a secure network location, download the installation packages for the OMT Installer and the products of your choice from the Software Licenses and Downloads portal.
This secure network location must be able to access your instance of Azure. -
-
You must be able to access the jumphost VM as root in the Azure cluster.
You can perform all steps from the jumphost. For more information, see Preparing the Jump Host Virtual Machine. -
The kubernetes command line tool
kubectl
is installed on your bastion and connected to your clusterIt is possible to perform the upgrade from another host, but you must still have
kubectl
connected to your cluster and proxy settings must be disabled. -
Any existing suite-upgrade-pod-arcsight-installer deployment has been deleted using this command:
kubectl delete deployment suite-upgrade-pod-arcsight-installer -n $(kubectl get namespaces | grep arcsight-installer | awk ' {print $1} ')
The command will return an error if no upgrade has been done previously -
(Conditional) If you are using custom data identifiers for Intelligence, ensure that you back up the
logstash-config-pipeline
config map that is accessible through the Kubernetes dashboard. -
(Conditional) If you have deployed the Intelligence capability, then perform Step 1 of the workaround described in the known issue Analytics Does Not Detect the Custom SQL Loader Scripts After the Intelligence Upgrade in the Release Notes for ArcSight Platform 23.3.
-
All pods are running, verify with this command:
kubectl get pods -A
Next Step: Running the ArcSight Platform OMT Upgrade (Azure)