Skip to main content

Global View OVA upgrade

This topic describes how to upgrade a Global View OVA (virtual appliance) deployment to version 2026.6.1. Upgrades run in place on the existing virtual machine: you update the deployment script and configuration, then redeploy the Global View application components with Helm.

OVA upgrade guidelines

Review the following guidelines before you upgrade a Global View OVA:

  • OVA-to-OVA upgrades are not supported: After you deploy the OVA as a virtual machine, perform all later Global View upgrades with the standard application upgrade process. Deploying a new OVA version over an existing VM is not supported.

  • Upgrades run in place on the existing VM: Once the Global View VM is deployed and running, you run all future upgrades on the same VM by upgrading the application components with Helm.

  • Review the version-specific upgrade notes first: Starting with Global View 2026.6.1, version-specific upgrade instructions are published for each release. Read the notes that match the version you are upgrading from.

  • Update the Helm values as required: Before you upgrade, review the applicable upgrade notes and make any required changes to the Helm values files in /home/virtana/templates/ , in particular templates/global-view-values.yaml . For the values changes specific to your source version, see the Global View upgrade (2026.6.1).

  • Run the standard deployment script: After you apply the configuration changes, run bash deploy.sh <deployment-type> to perform the upgrade.

Update deploy.sh before you upgrade to 2026.6.1

The deploy.sh script included in Global View OVA versions earlier than 2026.6.1 does not include the configuration changes introduced in Global View 2026.6.1. As a result, upgrades from earlier OVA versions to 2026.6.1 do not correctly update the image registry configuration and the Helm deployment options required for the following components:

  • Redis : The image repository name changes from redis to dhi-redis .

  • SeaweedFS : This component is new in 6.1 and requires image registry configuration.

  • VirtanaAI (Copilot) : The configuration keys move from the LiteLLM paths to the VirtanaAI paths.

  • CRD installation : The CRD deployment step must use the patched values file.

Before you run deploy.sh during the upgrade, apply the following updates to the existing script.

  1. Update the Redis image repository:

     sed -i \ 's|\.redis\.image\.repository = strenv(IMAGE_REGISTRY) + "/redis"|.redis.image.repository = strenv(IMAGE_REGISTRY) + "/dhi-redis"|g' \ deploy.sh

  2. Add the SeaweedFS image registry configuration:

     sed -i '/dhi-redis/a\ yq e -i '\''.seaweedfs.image.registry = strenv(IMAGE_REGISTRY)'\'' "$PATCHED_GLOBALVIEW_VALUES" ' deploy.sh

  3. Update the VirtanaAI configuration keys:

     sed -i \ -e 's/\.cp-configs\.litellm\.litellm_api_key/.cp-configs.virtana_ai.virtana_ai_api_key/g' \ -e 's/\.cp-configs\.litellm\.litellm_inference_endpoint/.cp-configs.virtana_ai.virtana_ai_inference_endpoint/g' \ deploy.sh

  4. Update the CRD deployment command so that CRD installation uses the patched values file:

     sed -i '/tags\.crds=true/ { /PATCHED_GLOBALVIEW_VALUES/! s|--set tags\.crds=true \\|--set tags.crds=true -f "$PATCHED_GLOBALVIEW_VALUES" \\| }' deploy.sh

Update the Global View version in input file

Update the Helm version variables and the VirtanaAI (Copilot) configuration in the input.env file before you run the upgrade.

Update the versions

Update GLOBAL_VIEW_HELM_VERSION and, optionally, CO_NORTH_HELM_VERSION in the input.env file to the latest versions available in the Virtana Helm repository. Run the following commands to find the latest available versions:

helm repo update  
helm search repo virtana-repo/virtana-global-view  
helm search repo virtana-repo/virtana-co-controller

Update the VirtanAI (Copilot) configuration

The OPENAI_API_KEY variable is replaced with a provider-based configuration model that supports OpenAI, Gemini, and LiteLLM. Update the VirtanaAI section of input.env as follows:

# Supported values: 
# OPENAI / GEMINI / LITELLM VIRTANA_AI_MODEL_PROVIDER='' 
# API key for OPENAI, GEMINI, or LITELLM VIRTANA_AI_API_KEY='' 
# Leave blank when using OPENAI or GEMINI. 
# For self-hosted LiteLLM deployments, 
# provide the LiteLLM endpoint URL. 
# Example: https://litellm.example.com VIRTANA_AI_INFERENCE_ENDPOINT=''

Variable

Description

Default value

VIRTANA_AI_MODEL_PROVIDER

AI provider for the VirtanaAI Copilot. Supported values: OPENAI , GEMINI , LITELLM .

—

VIRTANA_AI_API_KEY

API key for the selected provider (OpenAI, Gemini, or LiteLLM).

—

VIRTANA_AI_INFERENCE_ENDPOINT

Inference endpoint URL. Leave blank for OpenAI or Gemini. For a self-hosted LiteLLM deployment, provide the LiteLLM endpoint URL (for example, https://litellm.example.com ).

—

Download the image bundle (optional)

This step is required if any of the following conditions apply:

  • The VM does not have internet connectivity.

  • A private container image registry is not available in your environment.

  • You prefer to deploy using a pre-packaged image bundle.

To use the image bundle:

  • Obtain the release-specific image bundle file ( virtana-global-view-<GV_VERSION>-images-bundle.tgz ) from the Virtana Support team.

  • Copy the bundle file to the Virtana OVA VM in the /opt/virtana directory.

  • Do not extract the bundle manually. The deployment process extracts and loads the images automatically.

Customize or update the Helm values

You can customize the deployment by editing the Helm values template files before you upgrade. The template files are in /home/virtana/templates/ :

 ls -l /home/virtana/templates/

Update the appropriate values file to override the default configuration, such as resource requests and limits, storage settings, ingress configuration, node scheduling preferences, or application-specific parameters.

Note

Review the version-specific upgrade notes before you modify existing values files or upgrade, because configuration options and defaults can change between releases.

Run the upgrade

After you patch deploy.sh , update input.env , and adjust the Helm values, run the deployment script to upgrade Keycloak and Global View. To upgrade only Global View, upgrade Keycloak first, then Global View.

Action

Command

Upgrade Keycloak and Global View together

bash /home/virtana/deploy.sh all

Upgrade Keycloak only (step 1 of 2)

bash /home/virtana/deploy.sh keycloak

Upgrade Global View only (step 2 of 2)

bash /home/virtana/deploy.sh globalview

In this section: