Switching vProbe Java Version on NextGen Gateway Version 20.0.0

To switch the Java version used by vProbe between Java 11 and Java 17 on a NextGen Gateway (version 20.0.0), follow the steps below.
Before you begin,

  • Ensure that the gateway version is 20.0.0 before proceeding.
  • Ensure helm and kubectl are properly configured and you have access to the Kubernetes namespace where the NextGen Gateway is deployed.
  • Run all commands with appropriate permissions.
  • It is recommended to take a backup or snapshot of the environment before making changes.

To migrate vProbe from Java 11 to Java 17, run the following Helm upgrade command:

helm upgrade nextgen-gw oci://us-docker.pkg.dev/opsramp-registry/gateway-cluster-charts/nextgen-gw \
--version 20.0.0 \
--set vprobe.javaVersion=17 \
--reuse-values \
-n <namespace>

  • Replace < namespace > with the namespace where the NextGen Gateway is deployed.

To revert vProbe from Java 17 to Java 11 (if needed), run the following command:

helm upgrade nextgen-gw oci://us-docker.pkg.dev/opsramp-registry/gateway-cluster-charts/nextgen-gw \
--version 20.0.0 \
--set vprobe.javaVersion=11 \
--reuse-values \
-n <namespace>

  • Replace < namespace > with the namespace where the NextGen Gateway is deployed.

Post-Migration Validation

  1. Verify the Java Version in Use by vProbe Use the following command to check the Java version currently being used by the vProbe container:
    kubectl exec -it nextgen-gw-0 -c vprobe — java -version

You should see output similar to one of the following, depending on the version in use:

For Java 11:

openjdk version "11.0.28" 2025-07-15
OpenJDK Runtime Environment Temurin-11.0.28+6 (build 11.0.28+6)
OpenJDK 64-Bit Server VM Temurin-11.0.28+6 (build 11.0.28+6, mixed mode, sharing)

For Java 17:

openjdk 17.0.16 2025-07-15
OpenJDK Runtime Environment Temurin-17.0.16+8 (build 17.0.16+8)
OpenJDK 64-Bit Server VM Temurin-17.0.16+8 (build 17.0.16+8, mixed mode, sharing)
  1. Verify Gateway Tunnel Connectivity and Monitoring
  • Confirm that the NextGen Gateway tunnel is active and functioning.
  • Ensure monitoring is working correctly for all connected resources and services.