When you first upgrade to CDV v22.2.2 (or later) from a version prior to CDV v22.2.2, the state of currently-running visibility jobs are not retained. You must rerun discovery and visibility after the upgrade.
After you run discovery and visibility jobs on the upgraded version of Cloud Discovery & Visibility, the UDFs from the older version of Cloud Discovery & Visibility are replaced with the updated UDFs from the current version. There is no backwards compatibility and you cannot run an older version of Cloud Discovery & Visibility.
If you are upgrading Cloud Discovery & Visibility that was deployed on a BDDS, see Upgrading a container for details on upgrading the container.
Before you begin:
- Stop the Cloud Discovery & Visibility container by running the following
command:
docker stop <gateway_container_name> - Remove the Cloud Discovery & Visibility container by running the
following
command:
docker rm <gateway_container_name>Note: Removing the Cloud Discovery & Visibility container will not remove your workspace or logging data, as these are saved via directories mapped to either your local machine or Docker volume.
Upgrading your Cloud Discovery & Visibility container involves
executing the same docker run command used for installation and
mapping to your existing workspace and logging directories.
- From the host machine, run the following
command:
docker login quay.io - At the prompt, enter your Quay user name and password obtained when generating the encrypted password.
- Download the Cloud Discovery & Visibility Adaptive Application from Quay
using the following
command:
docker pull quay.io/bluecat/cloud_discovery_visibility:<latest_version> - Start the upgraded Cloud Discovery & Visibility image using the
following command:
docker run -d \ -p 80:8000 \ -p 443:44300 \ -v <path_to_mapped_log_directory>:/logs/ \ -e BAM_IP=<your_bam_ip_address> \ --name <gateway_container_name> \ quay.io/bluecat/cloud_discovery_visibility:<latest_version>